From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Zhang Rui <rui.zhang@intel.com>
Cc: "Kenneth R. Crudup" <kenny@panix.com>,
Linux PM list <linux-pm@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [Fwd: Commit 555c45fe0d0 ("int340X/processor_thermal_device: add support for MMIO RAPL") boot failure]
Date: Sat, 20 Jul 2019 14:09:55 +0200 [thread overview]
Message-ID: <1740115.QtvjdlHhER@kreacher> (raw)
In-Reply-To: <CAJZ5v0j7QxrWtY8h=GgHWjpTm37AhnpNe5j=zLY3v7EwGi94ig@mail.gmail.com>
On Saturday, July 20, 2019 12:18:39 PM CEST Rafael J. Wysocki wrote:
> On Sat, Jul 20, 2019 at 3:25 AM Zhang Rui <rui.zhang@intel.com> wrote:
> >
> > On 五, 2019-07-19 at 10:31 -0700, Kenneth R. Crudup wrote:
> > > On Fri, 19 Jul 2019, Zhang Rui wrote:
> > >
> > > >
> > > > please try the patch below and confirm if it helps or not.
> > > >
> > > > From: Zhang Rui <rui.zhang@intel.com>
> > > > Date: Fri, 19 Jul 2019 23:25:14 +0800
> > > > Subject: [PATCH] powercap: adjust init order
> > > The patch fixes the boot crash, yes.
> > >
> > Hi, Kenny,
> >
> > thanks for testing.
> >
> > Rafael,
> >
> > can we merge this urgent fix before the merge window closed?
>
> Well, we could try that, but it is not even in Patchwork ATM and it
> would be good to let it appear in linux-next too.
>
> Please resend it as a proper patch, so that Patchwork can pick it up
> and I'll queue it up and push it next week.
BTW, I picked it up from email, so it will appear in linux-next on Mon, but
I needed to fix it up to make it apply and I made some changes in the
subject and changelog.
Also, it would be good to explain in the changelog what exactly causes the
crash to occur.
Thanks!
next prev parent reply other threads:[~2019-07-20 12:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.21.1907181955330.2769@hp-x360>
[not found] ` <1563514893.2433.3.camel@intel.com>
2019-07-19 6:13 ` [Fwd: Commit 555c45fe0d0 ("int340X/processor_thermal_device: add support for MMIO RAPL") boot failure] Kenneth R. Crudup
2019-07-19 7:51 ` Rafael J. Wysocki
2019-07-19 13:03 ` Kenneth R. Crudup
2019-07-19 15:34 ` Zhang Rui
2019-07-19 17:31 ` Kenneth R. Crudup
2019-07-20 1:25 ` Zhang Rui
2019-07-20 10:18 ` Rafael J. Wysocki
2019-07-20 12:09 ` Rafael J. Wysocki [this message]
2019-07-19 8:30 ` Rafael J. Wysocki
2019-07-19 11:28 ` Zhang, Rui
2019-07-19 12:33 ` Zhang, Rui
2019-07-19 15:35 ` Zhang Rui
2019-07-20 12:11 ` Rafael J. Wysocki
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=1740115.QtvjdlHhER@kreacher \
--to=rjw@rjwysocki.net \
--cc=kenny@panix.com \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
/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