From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@fb.com>,
linux-nvme@lists.infradead.org, sagi@grimberg.me
Subject: Re: [PATCH] nvme: add bug report info for global duplicate id
Date: Tue, 7 Jun 2022 16:44:09 +0200 [thread overview]
Message-ID: <20220607144409.GA10262@lst.de> (raw)
In-Reply-To: <Yp9fUSEmf3hAoRfp@kbusch-mbp.dhcp.thefacebook.com>
On Tue, Jun 07, 2022 at 08:23:13AM -0600, Keith Busch wrote:
> > So I like the idea here, but this won't give us the PCI device id
> > that we usually need for quirks.
>
> Yeah, we don't have the DID from core. Should I add a driver specific op to
> print device info? Just a quick rough idea here:
Yes, something like this looks reasonable to me.
prev parent reply other threads:[~2022-06-07 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 16:40 [PATCH] nvme: add bug report info for global duplicate id Keith Busch
2022-06-06 17:15 ` Chaitanya Kulkarni
2022-06-07 10:15 ` Christoph Hellwig
2022-06-07 14:23 ` Keith Busch
2022-06-07 14:44 ` Christoph Hellwig [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=20220607144409.GA10262@lst.de \
--to=hch@lst.de \
--cc=kbusch@fb.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