From: Bjorn Helgaas <helgaas@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Bao, Joseph" <joseph.bao@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stuart Hayes <stuart.w.hayes@gmail.com>,
"kw@linux.com" <kw@linux.com>
Subject: Re: HW power fault defect cause system hang on kernel 5.4.y
Date: Wed, 17 Nov 2021 15:43:17 -0600 [thread overview]
Message-ID: <20211117214317.GA1777393@bhelgaas> (raw)
In-Reply-To: <20211117080035.GA18186@wunner.de>
On Wed, Nov 17, 2021 at 09:00:35AM +0100, Lukas Wunner wrote:
> On Tue, Nov 16, 2021 at 02:42:20AM +0000, Bao, Joseph wrote:
> > I've tested this tentative patch, and it fixes the issue.
>
> Bjorn, do you want me to resend the fix as a proper patch
> (instead of appended to an e-mail) for visibility?
Yes, please; I think it only made it into patchwork as a reply in the
email thread, not as the primary patch, so it'll be less likely to get
lost if you post it as a regular patch.
> If so, do you have any change requests that I should fold in?
>
> Link to the fix:
> https://lore.kernel.org/linux-pci/20211115192723.GA19161@wunner.de/
>
> Thanks,
>
> Lukas
prev parent reply other threads:[~2021-11-17 21:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 3:45 HW power fault defect cause system hang on kernel 5.4.y Bao, Joseph
2021-11-02 22:34 ` Bjorn Helgaas
2021-11-09 7:59 ` Bao, Joseph
2021-11-09 15:29 ` Bjorn Helgaas
2021-11-11 2:16 ` Bao, Joseph
2021-11-12 0:44 ` Krzysztof Wilczyński
2021-11-12 1:47 ` Bao, Joseph
2021-11-12 1:49 ` Krzysztof Wilczyński
2021-11-09 15:36 ` stuart hayes
2021-11-10 9:20 ` Bao, Joseph
2021-11-10 15:56 ` stuart hayes
2021-11-11 1:03 ` Bao, Joseph
2021-11-15 19:27 ` Lukas Wunner
2021-11-16 2:42 ` Bao, Joseph
2021-11-17 8:00 ` Lukas Wunner
2021-11-17 21:43 ` Bjorn Helgaas [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=20211117214317.GA1777393@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=joseph.bao@intel.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=stuart.w.hayes@gmail.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