From: Keith Busch <kbusch@kernel.org>
To: AlanCui4080 <me@alancui.cc>
Cc: linux-nvme@lists.infradead.org, Pascal Terjan <pterjan@google.com>
Subject: Re: The wrong usage of NVME_QUIRK_IGNORE_DEV_SUBNQN
Date: Fri, 8 May 2026 09:03:00 +0100 [thread overview]
Message-ID: <af2YtHjq3mhWiyJA@kbusch-mbp> (raw)
In-Reply-To: <EgTEZ7GYRxSc3ZRAxjIuBQ@alancui.cc>
On Fri, May 08, 2026 at 02:20:30AM +0800, AlanCui4080 wrote:
> Sorry for my bad, but the prior patch which is merged into mainline may
> be a mistake:
> nvme: add quirk NVME_QUIRK_IGNORE_DEV_SUBNQN for 144d:a808
> (7f991e3f9b8f044640bcb5fa8570350a68932843 at mainline).
Okay, please send a revert. The number of devices that got such
fundamental things wrong is truly astounding, so I generally just take
such reports and patches as a reaction to a real observation.
next prev parent reply other threads:[~2026-05-08 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 18:20 The wrong usage of NVME_QUIRK_IGNORE_DEV_SUBNQN AlanCui4080
2026-05-08 8:03 ` Keith Busch [this message]
2026-05-08 9:59 ` [PATCH] Revert "nvme: add quirk NVME_QUIRK_IGNORE_DEV_SUBNQN for 144d:a808" AlanCui4080
2026-05-11 15:01 ` Keith Busch
2026-05-08 10:11 ` The wrong usage of NVME_QUIRK_IGNORE_DEV_SUBNQN AlanCui4080
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=af2YtHjq3mhWiyJA@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=me@alancui.cc \
--cc=pterjan@google.com \
/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