From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: Re: [PATCH] nvme-pci: Netac has bogus namespace ids
Date: Tue, 29 Nov 2022 09:46:55 +0100 [thread overview]
Message-ID: <20221129084655.GA26082@lst.de> (raw)
In-Reply-To: <20221122112428.1573353-1-sagi@grimberg.me>
This seems to be the same device we just quirked with
"nvme-pci: add NVME_QUIRK_BOGUS_NID for Netac NV7000"
next prev parent reply other threads:[~2022-11-29 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 11:24 [PATCH] nvme-pci: Netac has bogus namespace ids Sagi Grimberg
2022-11-29 4:30 ` Chaitanya Kulkarni
2022-11-29 8:46 ` Christoph Hellwig [this message]
2022-11-30 8:26 ` Sagi Grimberg
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=20221129084655.GA26082@lst.de \
--to=hch@lst.de \
--cc=Chaitanya.Kulkarni@wdc.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 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.