From: Bean Huo <beanhuo@iokpp.de>
To: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Bean Huo <beanhuo@micron.com>
Subject: Re: [PATCH] nvme: skip I/O Command Set specific Identify Controller on pre-2.0 devices
Date: Wed, 06 May 2026 22:50:29 +0200 [thread overview]
Message-ID: <bbfffa354419f933e8c201bd8211f891298bd04a.camel@iokpp.de> (raw)
In-Reply-To: <aftCV3rDk3yeWA1d@kbusch-mbp>
On Wed, 2026-05-06 at 15:29 +0200, Keith Busch wrote:
> On Mon, May 04, 2026 at 06:36:55AM +0200, Christoph Hellwig wrote:
> > No. NVMe allow TPs to be implemented on devices claiming earlier
> > compliance. We've had this patch and this answer probably half a
> > dozen times now.
>
> The proper solution is that vendors need to have their controllers stop
> logging pointless errors that don't help anything.
Thanks Christoph, Keith.
I wasn't aware that TPs can be implemented independently of the spec version
claimed by the device. I'll drop this patch and follow up with the vendor
instead.
Kind regards,
Bean
prev parent reply other threads:[~2026-05-06 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 20:02 [PATCH] nvme: skip I/O Command Set specific Identify Controller on pre-2.0 devices Bean Huo
2026-05-04 4:36 ` Christoph Hellwig
2026-05-06 13:29 ` Keith Busch
2026-05-06 20:50 ` Bean Huo [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=bbfffa354419f933e8c201bd8211f891298bd04a.camel@iokpp.de \
--to=beanhuo@iokpp.de \
--cc=axboe@kernel.dk \
--cc=beanhuo@micron.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 \
/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