On Thu, Dec 13, 2012 at 3:20 AM, Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote: > On 12 December 2012 21:56, Mike Turquette <mturquette@xxxxxxxxxx> wrote: >> On Mon, Dec 10, 2012 at 7:25 AM, Ulf Hansson <ulf.hansson@xxxxxxxxxxxxxx> wrote: >>> From: Ulf Hansson <ulf.hansson@xxxxxxxxxx> >>> >>> This patchset starts by renaming the db8500 cpufreq driver to a more generic >>> name. There are new variants which rely on it too, so instead we give it a >>> family name of dbx500. >>> >>> On top of that a fixup patch for initialization of the driver and some minor >>> cleanup patches are included as well. >>> >>> These patches can be material for 3.8. >>> >>> Since some patches for the db8500 cpufreq driver has recently been merged >>> through Mike Turquette's clk tree, I decided to base these patches on top >>> of the clk-next branch. So I hope Mike is fine by merging these patches >>> through his tree. >>> >>> So I will try to collect ACKs from Rafael for the cpufreq patches. The >>> mfd patch has already been ACKED by Samuel. >>> >> >> Ulf, >> >> Just FYI clk-next has been pulled by Linus for 3.8. I can still take >> this branch once Rafael ACKs the CPUfreq bits if you want, but I think >> you have more options now that clk-next is merged in. It's up to you. > > I think the easiest way forward (at least for me :-) ) would be if we > could send them as for 3.8 rcs. Is that possible for you Mike? > Hi Ulf, I did not want to leave you hanging on this point. I decided at the last minute to not bring a development platform or a nice laptop on my vacation so I will not be sending any more pull requests to Linus for 3.8-rc unless some patches come in which are just obvious fixes. Even then I will wait until I return in January to properly test any fixes before I send the request out. Sorry that these patches did not make it in for 3.8 but I will queue them up into clk-next in January. Thanks, Mike >> >> Regards, >> Mike > > Thanks! > > Ulf Hansson -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
