From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: "Gagniuc, Alexandru" <alexandru.gagniuc@hp.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@fb.com" <axboe@fb.com>, "hch@lst.de" <hch@lst.de>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Zhang, Eniac" <eniac-xw.zhang@hp.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] nvme-pci: Add suspend quirk for HP mt645 thin client
Date: Mon, 10 Jul 2023 17:28:31 -0500 [thread overview]
Message-ID: <4edb1aad-af46-1489-0b59-cb122b409186@amd.com> (raw)
In-Reply-To: <SJ0PR84MB2088ABC543710226BB8889DC8F30A@SJ0PR84MB2088.NAMPRD84.PROD.OUTLOOK.COM>
On 7/10/2023 3:06 PM, Gagniuc, Alexandru wrote:
> [snip]
> Hi Mario,
>
> The product link you posted is correct. I was not aware of e2a56364485e
> when I developed the fix herein before v6.3. After some quick testing, I can
> confirm that e2a56364485e solves the original issue.
>
> We do not need this patch then.
>
> Thank you,
> Alex
>
Great, thanks for confirming. Just as an FYI to you we don't have any
intention
to grow that list any further. Those were added because the platforms
came at
a time that StorageD3Enable was just being introduced and there were
bugs with too
many missing it.
If you have future AMD based products that use newer hardware such as
Rembrandt or
Phoenix that you need to fix this in the BIOS properly.
prev parent reply other threads:[~2023-07-10 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 18:06 Alexandru Gagniuc
2023-07-08 4:28 ` Limonciello, Mario
2023-07-10 20:06 ` Gagniuc, Alexandru
2023-07-10 22:28 ` Limonciello, Mario [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=4edb1aad-af46-1489-0b59-cb122b409186@amd.com \
--to=mario.limonciello@amd.com \
--cc=alexandru.gagniuc@hp.com \
--cc=axboe@fb.com \
--cc=eniac-xw.zhang@hp.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®