On Tue, Mar 04, 2014 at 11:16:50AM -0800, Dirk Brandewie wrote: > On 03/04/2014 11:06 AM, Greg KH wrote: > >On Tue, Mar 04, 2014 at 10:59:30AM -0800, Dirk Brandewie wrote: > >>On 03/04/2014 10:58 AM, Greg KH wrote: > >>>On Tue, Mar 04, 2014 at 10:43:00AM -0800, dirk.brandewie@xxxxxxxxx wrote: > >>>>From: Dirk Brandewie <dirk.j.brandewie@xxxxxxxxx> > >>>> > >>>>A documentation update exposed the existance of the turbo ratio > >>>>register. Update baytrail support to use the turbo range. > >>>> > >>>>Signed-off-by: Dirk Brandewie <dirk.j.brandewie@xxxxxxxxx> > >>>>Cc: 3.13+ <stable@xxxxxxxxxxxxxxx> # 3.13.x: 007bea09 intel_pstate: Add setting > >>>>Cc: 3.13+ <stable@xxxxxxxxxxxxxxx> # 3.13+ > >>>>Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx> > >>>>--- > >>>> drivers/cpufreq/intel_pstate.c | 15 ++++++++++++--- > >>>> 1 file changed, 12 insertions(+), 3 deletions(-) > >>> > >>>What is the upstream git commit id of this patch? > >>> > >> > >>007bea098b869 intel_pstate: Add setting voltage value for baytrail P states. > >>61d8d2abc15e9 intel_pstate: Add support for Baytrail turbo P states > > > >Why did you mush these together? Please backport the individual > >patches, I don't want things diverging in the stable trees. > > > > I was trying to follow the procedure in stable_kernel_rules.txt for specifying > prerequisites. Yes, that works for commits you get merged into Linus's tree, but this is totally confusing me. > Both patches apply cleanly to v3.13.5 no changes required. Which is "both"? > I will send both patches with their upsteam commit ID's Thanks, consider me someone with no short-term memory... -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html