Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752534AbaBSAid (ORCPT ); Tue, 18 Feb 2014 19:38:33 -0500 Received: from v094114.home.net.pl ([79.96.170.134]:60940 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752235AbaBSAic (ORCPT ); Tue, 18 Feb 2014 19:38:32 -0500 From: "Rafael J. Wysocki" To: Dirk Brandewie Cc: "dirk.j.brandewie@intel.com" , "linux-pm@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 0/5] intel_pstate updates for v3.14-rcX Date: Wed, 19 Feb 2014 01:53:22 +0100 Message-ID: <2254366.ixXkMqbYNC@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/3.13.0+; KDE/4.11.5; x86_64; ; ) In-Reply-To: <5303FC4E.7040305@gmail.com> References: <1392228067-14817-1-git-send-email-dirk.j.brandewie@intel.com> <1862084.mmnlZ4yS6m@vostro.rjw.lan> <5303FC4E.7040305@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, February 18, 2014 04:35:26 PM Dirk Brandewie wrote: > On 02/18/2014 04:43 PM, Rafael J. Wysocki wrote: > > On Tuesday, February 18, 2014 04:24:02 PM Dirk Brandewie wrote: > >> On Tuesday, February 18, 2014, Rafael J. Wysocki wrote: > >> > >>> On Tuesday, February 18, 2014 03:53:48 PM Dirk Brandewie wrote: > >>>> On 02/18/2014 02:27 PM, Rafael J. Wysocki wrote: > >>>>> On Tuesday, February 18, 2014 12:29:54 PM Dirk Brandewie wrote: > >>>>>> Hi Rafael, > >>>>> > >>>>> Hi, > >>>>> > >>>>>> On 02/12/2014 10:01 AM, dirk.brandewie@gmail.com wrote: > >>>>>>> From: Dirk Brandewie > > >>>>>>> > >>>>>>> Based on v3.14-rc2 > >>>>>>> > >>>>>>> Patch 1 removes energy reporting the patch from Maurizio Lambardi > >>>>>>> intel_pstate: fix race condition in intel_pstate_init() can be > >>> dropped. > >>>>>>> > >>>>>> > >>>>>> Any reason why patches 2-5 did not make rc3 other than timing? > >>>>>> > >>>>>> Patches 2/3 can easily wait for v3.15.x > >>>>>> > >>>>>> Patches 4/5 fix bugs that are in the wild. > >>>>> > >>>>> I asked you about them, but you didn't reply: > >>>>> > >>>>> http://marc.info/?l=linux-pm&m=139225158531023&w=4 > >>>>> > >>>>> Again, do patches [4-5/5] depend on [2-3/5]? > >>>>> > >>>>> If not, I can queue them up for -rc4. > >>>> > >>>> All the patches are independent of one another. > >>>> > >>>> Patch 2 is straight cleanup no functional change but reduces the memory > >>>> footprint slightly. > >>>> > >>>> Patch 3 is a bug that will only be seen when the PID is reset at init > >>> time > >>>> or when a change is made to PID params via debugfs. The problem will > >>> only > >>>> exist for one sample time since it is setting last_err in the PID. > >>>> > >>>> Patch 4-5 are bugs found during Baytrail-T testing > >>> > >>> Are there any pointers to bug reports that may be included in the > >>> changelogs > >>> of these? > >> > >> > >> No. I got the reports via email. I could probably get the reporters to > >> file bugzillas. > > > > It would be good to add information about what machines are affected > > and what the user-visible problems are to the changelogs for future > > reference. > > > > And do we want these two patches in -stable? If so, what -stable series should > > they go into? > > Patch 2 v3.10+ > > Patch 3 v3.12+ You said [2-3/5] were cleanups, so why do you think they are -stable material? > Patch 4/5 v3.13+ OK What about the bug information? Can you please point me to the e-mail threads where the bugs were discussed at least? Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/