From: Christoph Hellwig <hch@lst.de>
To: "Javier.gonz@samsung.com" <Javier.gonz@samsung.com>
Cc: "Grochowski, Maciej" <Maciej.Grochowski@sony.com>,
Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"Lewis, Nathaniel" <Nathaniel.Lewis@sony.com>
Subject: Re: [PATCH] nvme-pci: fix resume after AER recovery
Date: Mon, 6 Feb 2023 16:42:18 +0100 [thread overview]
Message-ID: <20230206154218.GA12556@lst.de> (raw)
In-Reply-To: <20230206140220.6af2b6k7belue2nh@ArmHalley.local>
On Mon, Feb 06, 2023 at 03:02:20PM +0100, Javier.gonz@samsung.com wrote:
> Is there a chance we can get a quirk for this for this FW. Seems like an
> issue on our side that is creating problems.
So waht would the quirk look like? This would have to be something in
the core PCIe code, not NVMe as far as I can tell.
next prev parent reply other threads:[~2023-02-06 16:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 10:14 [PATCH] nvme-pci: fix resume after AER recovery Christoph Hellwig
2023-01-30 18:35 ` Keith Busch
2023-01-30 18:43 ` Keith Busch
2023-01-30 18:54 ` Grochowski, Maciej
2023-01-31 8:58 ` Christoph Hellwig
2023-01-31 15:22 ` Keith Busch
2023-02-01 22:58 ` Grochowski, Maciej
2023-02-02 10:18 ` Christoph Hellwig
2023-02-02 18:47 ` Grochowski, Maciej
2023-02-02 19:43 ` Keith Busch
2023-02-03 1:29 ` Grochowski, Maciej
2023-02-03 1:37 ` Keith Busch
2023-02-03 18:45 ` Grochowski, Maciej
2023-02-06 14:02 ` Javier.gonz
2023-02-06 15:42 ` Christoph Hellwig [this message]
2023-02-06 16:22 ` Keith Busch
2023-02-06 17:51 ` Javier.gonz
2023-02-07 1:51 ` Grochowski, Maciej
2023-02-07 8:29 ` Javier.gonz
2023-02-07 10:36 ` Klaus Jensen
2023-02-07 19:05 ` Grochowski, Maciej
2023-02-08 6:43 ` Klaus Jensen
2023-02-08 17:26 ` Grochowski, Maciej
2023-02-08 17:39 ` Keith Busch
2023-02-08 22:38 ` Grochowski, Maciej
2023-02-09 7:55 ` Javier.gonz
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=20230206154218.GA12556@lst.de \
--to=hch@lst.de \
--cc=Javier.gonz@samsung.com \
--cc=Maciej.Grochowski@sony.com \
--cc=Nathaniel.Lewis@sony.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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