From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Keith Busch <kbusch@fb.com>,
linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: Re: [PATCHv2] nvme: add bug report info for global duplicate id
Date: Mon, 13 Jun 2022 17:04:32 +0200 [thread overview]
Message-ID: <20220613150432.GA6424@lst.de> (raw)
In-Reply-To: <YqdPaiDGtg+JuBug@kbusch-mbp.dhcp.thefacebook.com>
On Mon, Jun 13, 2022 at 08:53:30AM -0600, Keith Busch wrote:
> This problem seems more widespread than expected, so I think it would help to
> apply this patch now.
Yes, that's the plan. But as Jens was out for last week I didn't
bother with a pull request.
> And since this appears to be a gap in compliance testing, I feel I should
> report this. I think UNH is still handling compliance certification.
UNH provides the test suite, but the specs are handled in the nvme
interoperability workgroup. I already asked them to test this, but
nothing happened, but I think you asking again is definitively a good
idea.
next prev parent reply other threads:[~2022-06-13 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 15:30 [PATCHv2] nvme: add bug report info for global duplicate id Keith Busch
2022-06-13 14:53 ` Keith Busch
2022-06-13 15:04 ` Christoph Hellwig [this message]
2022-06-13 16:21 ` Keith Busch
2022-06-13 17:57 ` Christoph Hellwig
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=20220613150432.GA6424@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