Move OMAP2+ over to common clk framework
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest posting 2/20 of 26 patches 0 repliesNew
- v2 posting 1/20 of 26 patches 0 repliesSuperseded
Patches in v2 posting 2/2 No applies recorded yet
None of the 26 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 00/26] Move OMAP2+ over to common clk framework
Quoted 7 lines · Paul Walmsley
Hi
With the fixes that have been posted, this is testing clean here. Mike and Rajendra have put in months of work on these patches under often-difficult conditions, and it's really great that we've arrived at this point with zero obvious remaining regressions from the current code.
That's excellent news :)
Quoted 15 lines
The branch has been posted for the time being at
git://git.pwsan.com/linux-2.6in the branch 'common_clk_devel_3.8', with the head at commit376676b429cb6dc95c39cdac82b2be816ea22893, in case anyone else wants to try it.Anyway, barring any further regressions that haven't reared their ugly heads yet, and barring anything truly horrible in the code or data that I've missed so far, will take this branch from here. It still needs some more work before it's ready to merge. The clockdomain usecounting fix patch needs to be split and moved earlier in the patch stack so 'git bisect' doesn't result in warnings and broken PM on OMAP3. And it all is going to be rebased on the second set of PRCM cleanup patches at commit
b99db36cdf37decb1b5575c5f293d170cbbc53d6, which I'm assuming Tony is planning to pull. Then will plan to send that pull request to Tony.
Quoted 3 lines
Then after that, if there's still time to merge some of the clock changes that have showed up on the lists for 3.8, those will get stacked onto a topic branch based on the branch that's sent to Tony.
Sounds good to me.
Thanks,
Tony