From: Pankaj Raghav <p.raghav@samsung.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>,
<stable@vger.kernel.org>, Keith Busch <kbusch@kernel.org>,
Jens Axboe <axboe@fb.com>, Sagi Grimberg <sagi@grimberg.me>,
<linux-nvme@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<p.raghav@samsung.com>, <javier.gonz@samsung.com>
Subject: Re: [PATCH 1/1] nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM173X
Date: Thu, 27 Apr 2023 09:37:52 +0200 [thread overview]
Message-ID: <20230427073752.3e3spo2vgfxdfcv2@localhost> (raw)
In-Reply-To: <20230414051259.GA11464@lst.de>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
Hi Christoph,
On Fri, Apr 14, 2023 at 07:12:59AM +0200, Christoph Hellwig wrote:
> On Tue, Mar 21, 2023 at 02:26:04PM +0100, Christoph Hellwig wrote:
> > Can you send a patch with a new quirk that just disables the EUI64,
> > but keeps the NGUID?
>
> Did this go anywhere?
We had a discussion about this internally with our firmware team, and it
looks like these firmware were given to specific customers based on
mutual agreement. They are already in discussion with our firmware team
regarding this.
I don't think this should go into as a generic quirk in Linux for these
models.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2023-04-27 7:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 22:34 [PATCH 1/1] nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM173X Saeed Mirzamohammadi
2023-03-15 22:38 ` Chaitanya Kulkarni
2023-03-16 5:15 ` Christoph Hellwig
2023-03-16 21:31 ` Saeed Mirzamohammadi
2023-03-17 7:33 ` Christoph Hellwig
[not found] ` <CGME20230317111849eucas1p115741dc29cc0a5c57914e60aa5216288@eucas1p1.samsung.com>
2023-03-17 11:10 ` Pankaj Raghav
2023-03-17 16:26 ` Saeed Mirzamohammadi
2023-03-20 13:21 ` Pankaj Raghav
2023-03-21 13:26 ` Christoph Hellwig
2023-04-14 5:12 ` Christoph Hellwig
[not found] ` <CGME20230427074641eucas1p185bb564521b6c01366293d20970fdfe2@eucas1p1.samsung.com>
2023-04-27 7:37 ` Pankaj Raghav [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=20230427073752.3e3spo2vgfxdfcv2@localhost \
--to=p.raghav@samsung.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=javier.gonz@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=saeed.mirzamohammadi@oracle.com \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).