On Thursday 04 April 2013 08:04 PM, Santosh Shilimkar wrote: > On Thursday 04 April 2013 04:22 AM, Kevin Hilman wrote: >> Hi Santosh, >> >> Santosh Shilimkar <santosh.shilimkar@xxxxxx> writes: >> >>> Here is the refreshed version(v2) of the OMAP5 PM suspport which was posted >>> earlier (March 1st 2013). Patch-set incorporates comments from Nishant >>> Menon (Thanks for review NM) and his acked-by tags. I would like to get this >>> queued for 3.10 merge window if you are ok with the series. >> >> I did a review of this series with several comments on the individual >> patches. >> > Thanks a lot Kevin. I have addressed all the comments and have > updated patches ready. > >> I've already queued most of the CPUidle fixes/cleanups in my >> for_3.10/cleanup/cpuidle branch and will get that to Tony soon. For the >> rest, I suggest probably breaking it up into cleanup/consolidation stuff >> and then OMAP5 support. The latter will depend on all the OMAP5 >> data/headers but the cleanup/consolidation stuff could be merged sooner >> (but probably a bit late for v3.10 now.) >> > I have already split the patch-set into 'consolidation' and 'OMAP5 > support' since it was straight forward. Need to just build the > branches on top of your branches. So waiting for you to update > your 'for_3.10/*' branches. > > For the merge, its your call:) > As you said OMAP5 support(couple of patches) has a dependency > on OMAP5 data files. I will at least make the branches ready on > top of yours. > After looking at your tree, looks like the branches are already there. Idle branch name is not for_3.10/fixes/cpuidle though :) So I created 'for_3.10/omap_pm-cleanup' and 'for_3.10/omap5_pm_v2' and pushed on my git tree [1] in case you would like to have a look. I briefly tested them on OMAP4 device with CPUidle enabled and they seems to work fine. Will do OMAP5 testing tomorrow and then post the updated patches on list. Regards, Santosh [1] git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux.git -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
