SPEAr: Move to common clock framework
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 13 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 13 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 00/13] SPEAr: Move to common clock framework
Quoted 4 lines · Mike
I've taken patches 02 - 06 into my -next branch. Patch 01 isn't for me really, and I've not yet tested patch 07 (I'll take it everything looks good). The rest of your series (08 - 13) should probably go through Arnd.
My preference would be to have the whole series go through your tree and move the implementation of the spear clock code to drivers/clk in the process. This will reduce interdependencies between the spear clock branch and other branches that have spear patches.
I also think it's a good idea if you submit the clk patches to Linus directly for the next merge window, but it's ok to use arm-soc if that makes you feel more confident about it.
Arnd