From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@meta.com>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: fix cns check
Date: Tue, 15 Oct 2024 17:16:52 +0200 [thread overview]
Message-ID: <20241015151652.GA12532@lst.de> (raw)
In-Reply-To: <Zw5930diGlfHACzF@kbusch-mbp>
On Tue, Oct 15, 2024 at 08:36:15AM -0600, Keith Busch wrote:
> I like this idea, and the spec makes it seem safe enough to assume the
> tertiary version number is always 0 for 1.0 and 1.1 controllers. So
> yeah, this looks good to me.
Do you want to pick this up, or do you want me to send a patch?
next prev parent reply other threads:[~2024-10-15 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 21:40 [PATCH] nvme: fix cns check Keith Busch
2024-10-10 7:56 ` Christoph Hellwig
2024-10-10 15:11 ` Keith Busch
2024-10-11 8:09 ` Christoph Hellwig
2024-10-15 14:36 ` Keith Busch
2024-10-15 15:16 ` Christoph Hellwig [this message]
2024-10-15 15:20 ` Keith Busch
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=20241015151652.GA12532@lst.de \
--to=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-nvme@lists.infradead.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