All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Bean Huo <beanhuo@iokpp.de>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@lst.de>, 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: Mon, 4 May 2026 06:36:55 +0200	[thread overview]
Message-ID: <20260504043655.GA9013@lst.de> (raw)
In-Reply-To: <20260503200243.2968366-1-beanhuo@iokpp.de>

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.


  reply	other threads:[~2026-05-04  4:37 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 [this message]
2026-05-06 13:29   ` Keith Busch
2026-05-06 20:50     ` Bean Huo

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=20260504043655.GA9013@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=beanhuo@iokpp.de \
    --cc=beanhuo@micron.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.