From: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>
To: Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>
Cc: Pankaj Raghav <p.raghav@samsung.com>,
Christoph Hellwig <hch@lst.de>,
"stable@vger.kernel.org" <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-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"javier.gonz@samsung.com" <javier.gonz@samsung.com>
Subject: Re: [PATCH 1/1] nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM173X
Date: Wed, 28 Aug 2024 10:27:53 +0000 [thread overview]
Message-ID: <20240828102753.msxe2owymg42zwqp@quentin> (raw)
In-Reply-To: <53369ABE-DB4F-44B0-831C-E4CB232A949A@oracle.com>
On Tue, Aug 27, 2024 at 07:08:15PM +0000, Saeed Mirzamohammadi wrote:
> Hi Pankaj/Samsung team,
>
> Sorry for pulling up an old thread. Has this been fixed in the firmware? If not, we could fix this issue with quirk for now until it’s resolved on the firmware side.
Hi Saeed,
As I said before, this was specifically requested by the customer. I
would highly encourage you to get in touch with the firmware team in
Samsung.
So I still don't think this should go as a generic quirk.
<snip>
> >> 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.
>
--
Pankaj Raghav
next prev parent reply other threads:[~2024-08-28 10:28 UTC|newest]
Thread overview: 14+ 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
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
2023-04-27 7:37 ` Pankaj Raghav
2024-08-27 19:08 ` Saeed Mirzamohammadi
2024-08-28 10:27 ` Pankaj Raghav (Samsung) [this message]
2024-08-28 11:02 ` javier.gonz
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=20240828102753.msxe2owymg42zwqp@quentin \
--to=kernel@pankajraghav.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=p.raghav@samsung.com \
--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