Messages in this thread | | | Date | Wed, 14 Mar 2012 23:41:12 -0400 | From | Dave Jones <> | Subject | Re: linux-next: manual merge of the cpufreq tree with the cpufreq-current tree |
| |
On Thu, Mar 15, 2012 at 01:23:52PM +1100, Stephen Rothwell wrote: > Hi Dave, > > Today's linux-next merge of the cpufreq tree got a conflict in > drivers/cpufreq/Makefile between commit b09db45c56c2 ("cpufreq: OMAP > driver depends CPUfreq tables") from the cpufreq-current tree and commit > a35c50510dd4 ("EXYNOS4X12: Add support cpufreq for EXYNOS4X12") from the > cpufreq tree. > > Just context changes. I fixed it up (see below) and can carry the fix as > necessary.
Argh, I've managed to get "for 3.4" patches on my fixes branch by mistake. Given how close we are to 3.3 now, I'll just have Linus pull both branches when 3.4 opens up.
thanks for catching this.
Dave
| |