cpufreq: OMAP: fixes for v3.7-rc2
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 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 0/4] cpufreq: OMAP: fixes for v3.7-rc2
Quoted 23 lines · Rafael J. Wysocki
Quoted 13 lines · On Wednesday 03 of October 2012 16:00:25 Kevin Hilman wrote:
From: Kevin Hilman <[email protected]>
Here's a series with a couple bug fixes and a couple fixes that make this driver support newer OMAP-based SoCs.
The '
get_cpu_device' patch is needed due to a change in the OMAP OMAP PM core code which enforces use ofget_cpu_device()instead of a deprecated OMAP-specific API.The usage of plat/*.h headers breaks single zImage, so platforms are cleaning up and/or removing plat/*.h so the driver needs to be fixed accordingly.
Quoted 8 lines
This series is based on the merge of Rafael's pm-for-3.7-rc1 tag into Linus' master branch: commit
16642a2e7be23bbda013fc32d8f6c68982eab603.Tested CPUfreq on OMAP platforms: 3430/n900, 3530/Overo, 3730/OveroSTORM, 3730/Beagle-XM, 4430/Panda.
Rafael, if you're OK with this series, I'll get a pull request ASAP so it can be included for v3.7-rc2.
Quoted 7 lines
The patches are fine by me, but there may be a bit of a timing issue with them, because I'll be travelling between October 12 and October 21 inclusive and I won't be pushing stuff to kernel.org during that time.
So I think it would be better to merge this material through the arm-soc tree, if that's not a problem. If you decide to do so, please feel free to add my ACK to the patches.
Thanks, I'll get them queued.
Kevin