From: Pankaj Raghav <pankydev8@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbusch@kernel.org, sagi@grimberg.me, monish.kumar.r@intel.com,
Jason@zx2c4.com, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: move the Samsung X5 quirk entry to the core quirks
Date: Fri, 17 Jun 2022 16:53:42 +0200 [thread overview]
Message-ID: <20220617145342.ktideod25ndexioy@quentin> (raw)
In-Reply-To: <20220617083206.1146088-1-hch@lst.de>
On Fri, Jun 17, 2022 at 10:32:06AM +0200, Christoph Hellwig wrote:
> This device shares the PCI ID with the Samsung 970 Evo Plus that
> does not need or want the quirks. Move the the quirk entry to the
> core table based on the model number instead.
>
Can you add the thread that has the report in the commit log for
traceability?
https://lore.kernel.org/lkml/CAHmME9pwz4q0m-pSUy7ReWu4nNzxySNcYZrqyDZiTuGxHN=1NQ@mail.gmail.com/
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
Reviewed-by: Pankaj Raghav <p.raghav@samsung.com>
next prev parent reply other threads:[~2022-06-17 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 8:32 [PATCH] nvme: move the Samsung X5 quirk entry to the core quirks Christoph Hellwig
2022-06-17 14:53 ` Pankaj Raghav [this message]
2022-06-17 15:00 ` Jason A. Donenfeld
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=20220617145342.ktideod25ndexioy@quentin \
--to=pankydev8@gmail.com \
--cc=Jason@zx2c4.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=monish.kumar.r@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox