From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Erwan Velu <e.velu@criteo.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Erwan Velu <erwanaliasr1@gmail.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
"open list:INTEL PSTATE DRIVER" <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6] cpufreq: intel_pstate: Reporting reasons why driver prematurely exit
Date: Thu, 14 Feb 2019 18:31:54 +0100 [thread overview]
Message-ID: <CAJZ5v0gHvZwUuhOepgsUZ3OZZ4X4iGTA3LXOwMi3SYVj7F=iYA@mail.gmail.com> (raw)
In-Reply-To: <8158d558-bbcd-fabe-6c8a-8de840807dc0@criteo.com>
On Thu, Feb 14, 2019 at 5:42 PM Erwan Velu <e.velu@criteo.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.
prev parent reply other threads:[~2019-02-14 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 12:21 [PATCH v6] cpufreq: intel_pstate: Reporting reasons why driver prematurely exit Erwan Velu
2019-02-14 9:28 ` Erwan Velu
2019-02-14 10:22 ` Rafael J. Wysocki
2019-02-14 15:18 ` Erwan Velu
2019-02-14 17:30 ` Rafael J. Wysocki
2019-02-14 16:42 ` Erwan Velu
2019-02-14 17:31 ` Rafael J. Wysocki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJZ5v0gHvZwUuhOepgsUZ3OZZ4X4iGTA3LXOwMi3SYVj7F=iYA@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=e.velu@criteo.com \
--cc=erwanaliasr1@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).