From: "hch@lst.de" <hch@lst.de>
To: Xander Li <Xander_Li@kingston.com.tw>
Cc: Bart Van Assche <bvanassche@acm.org>,
"paulburton@kernel.org" <paulburton@kernel.org>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@fb.com" <axboe@fb.com>, "hch@lst.de" <hch@lst.de>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ralf@linux-mips.org" <ralf@linux-mips.org>,
"jhogan@kernel.org" <jhogan@kernel.org>,
"christian@brauner.io" <christian@brauner.io>,
"jeff_yang@kingston.corp-partner.google.com"
<jeff_yang@kingston.corp-partner.google.com>,
"dora_chueh@kingston.corp-partner.google.com"
<dora_chueh@kingston.corp-partner.google.com>,
"james_liu@kingston.corp-partner.google.com"
<james_liu@kingston.corp-partner.google.com>,
Vincent Wu <Vincent_Wu@kingston.com.tw>
Subject: Re: [patch] nvme-pci: disable Write_Zeroes on Kingston SSD
Date: Mon, 10 Oct 2022 10:20:44 +0200 [thread overview]
Message-ID: <20221010082044.GA23747@lst.de> (raw)
In-Reply-To: <CO1PR10MB4691DEAA88F86F001ACA5A1CCB5D9@CO1PR10MB4691.namprd10.prod.outlook.com>
On Wed, Oct 05, 2022 at 10:01:11AM +0000, Xander Li wrote:
>
> drivers/nvme/host/pci.c | 10 ++++++++++
>
> 1 file changed, 10 insertions(+)
>
>
>
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
>
> index 98864b853eef..d08c8c854f3a 100644
>
> --- a/drivers/nvme/host/pci.c
>
> +++ b/drivers/nvme/host/pci.c
This patch seems very white space damaged.
>
> @@ -3503,6 +3503,16 @@ static const struct pci_device_id nvme_id_table[] = {
>
> .driver_data = NVME_QUIRK_NO_DEEPEST_PS, },
>
> { PCI_DEVICE(0x2646, 0x2263), /* KINGSTON A2000 NVMe SSD */
>
> .driver_data = NVME_QUIRK_NO_DEEPEST_PS, },
>
> + { PCI_DEVICE(0x2646, 0x5018), /* KINGSTON OM8SFP4xxxxP OS21012 NVMe SSD */
>
> + .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
>
> + { PCI_DEVICE(0x2646, 0x5016), /* KINGSTON OM3PGP4xxxxP OS21011 NVMe SSD */
>
> + .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
>
> + { PCI_DEVICE(0x2646, 0x501A), /* KINGSTON OM8PGP4xxxxP OS21005 NVMe SSD */
>
> + .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
>
> + { PCI_DEVICE(0x2646, 0x501B), /* KINGSTON OM8PGP4xxxxQ OS21005 NVMe SSD */
>
> + .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
>
> + { PCI_DEVICE(0x2646, 0x501E), /* KINGSTON OM3PGP4xxxxQ OS21011 NVMe SSD */
>
> + .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
>
> { PCI_DEVICE(0x1e4B, 0x1001), /* MAXIO MAP1001 */
>
> .driver_data = NVME_QUIRK_BOGUS_NID, },
>
> { PCI_DEVICE(0x1e4B, 0x1002), /* MAXIO MAP1002 */
>
> --
>
> 2.25.1
>
>
>
>
>
>
> Xander Li
> Technical Resources Group
> Kingston Technology Far East Corp.
> Office Line: +886-3-5641539 Ext.6135
> E-mail: xander_li@kingston.com.tw<mailto:xander_li@kingston.com.tw>
>
> This email and attachment(s) may contain material that is confidential, privileged and/or attorney work product for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
---end quoted text---
next parent reply other threads:[~2022-10-10 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CO1PR10MB4691DEAA88F86F001ACA5A1CCB5D9@CO1PR10MB4691.namprd10.prod.outlook.com>
2022-10-10 8:20 ` hch [this message]
2022-10-11 11:06 [PATCH] nvme-pci: disable write zeroes on Kingston SSD Xander Li
2022-10-16 5:14 ` Chaitanya Kulkarni
2022-10-17 7:20 ` Christoph Hellwig
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=20221010082044.GA23747@lst.de \
--to=hch@lst.de \
--cc=Vincent_Wu@kingston.com.tw \
--cc=Xander_Li@kingston.com.tw \
--cc=axboe@fb.com \
--cc=bvanassche@acm.org \
--cc=christian@brauner.io \
--cc=dora_chueh@kingston.corp-partner.google.com \
--cc=james_liu@kingston.corp-partner.google.com \
--cc=jeff_yang@kingston.corp-partner.google.com \
--cc=jhogan@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=paulburton@kernel.org \
--cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox