[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gHvZwUuhOepgsUZ3OZZ4X4iGTA3LXOwMi3SYVj7F=iYA@mail.gmail.com>
Date: Thu, 14 Feb 2019 18:31:54 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Erwan Velu <e.velu@...teo.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Erwan Velu <erwanaliasr1@...il.com>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Len Brown <lenb@...nel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Viresh Kumar <viresh.kumar@...aro.org>,
"open list:INTEL PSTATE DRIVER" <linux-pm@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6] cpufreq: intel_pstate: Reporting reasons why driver
prematurely exit
On Thu, Feb 14, 2019 at 5:42 PM Erwan Velu <e.velu@...teo.com> wrote:
>
>
> Le 14/02/2019 à 11:22, Rafael J. Wysocki a écrit :
> > I've queued it up with some manual changes. No need to update.
>
> As this could help troubleshooting platforms and as some commits like
> the PSS one on Proliant servers were backported to stable, I would
> surely make sense to backport it to the other stable.
>
> I know this is only a trivial print patch but as my initial issue
> started with some of the 4.14 serie, it could be nice to have it too.
You can always request -stable to pick up a patch once it's got to the mainline.
I'm not going to mark it as -stable material, though, as it is not a
fix strictly speaking.
Powered by blists - more mailing lists