public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: user090909 <fuckgithub@riseup.net>
To: busch@kernel.org, axboe@fb.com, sagi@grimberg.me,
	linux-nvme@lists.infradead.org
Subject: [PATCH] Add quirk for ADATA SX6000PNP
Date: Mon, 26 Dec 2022 14:15:39 +0000	[thread overview]
Message-ID: <ed916236ae7f2823aeccc8a85230abe5@riseup.net> (raw)

From 65e5a06268a4510f2858cbd182dbc60caf7003ff Mon Sep 17 00:00:00 2001
From: user090909 <fuckgithub@riseup.net>
Date: Mon, 26 Dec 2022 17:12:54 +0300
Subject: [PATCH] Add quirk for ADATA SX6000PNP

Signed-off-by: user090909 <fuckgithub@riseup.net>
---
 drivers/nvme/host/pci.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index f0f8027644bb..ca48d0b229e8 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -3415,6 +3415,9 @@ static const struct pci_device_id nvme_id_table[]
= {
 	{ PCI_DEVICE(0x10ec, 0x5762),   /* ADATA SX6000LNP */
 		.driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN |
 				NVME_QUIRK_BOGUS_NID, },
+	{ PCI_DEVICE(0x10ec, 0x5763),   /* ADATA SX6000PNP */
+                .driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN |
+                                NVME_QUIRK_BOGUS_NID, },
 	{ PCI_DEVICE(0x1cc1, 0x8201),   /* ADATA SX8200PNP 512GB */
 		.driver_data = NVME_QUIRK_NO_DEEPEST_PS |
 				NVME_QUIRK_IGNORE_DEV_SUBNQN, },
-- 
2.39.0



             reply	other threads:[~2022-12-26 14:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 14:15 user090909 [this message]
2022-12-28 19:20 ` [PATCH] Add quirk for ADATA SX6000PNP Keith Busch
2023-01-08 17:17   ` Christoph Hellwig
2023-02-17 13:27 ` user090909
  -- strict thread matches above, loose matches on Subject: below --
2023-02-10 12:08 Ivan Rubinov
2023-02-13 10:22 ` Sagi Grimberg
2023-02-10 12:10 Ivan Rubinov
2023-02-13  6:08 ` Christoph Hellwig
2023-02-13 10:13   ` Daniel Wagner
     [not found]     ` <a0526a5ef8a1f7bb199231609df7baef@riseup.net>
2023-02-16 13:25       ` Daniel Wagner
2023-02-17 13:28 ` Ivan Rubinov
2023-02-23 14:53   ` Daniel Wagner
     [not found]     ` <63b276e4-a7eb-f493-fdf7-8dc343aaff50@riseup.net>
2023-02-24  8:57       ` Daniel Wagner
     [not found]         ` <f8ba7be0-37f4-0c5f-373b-2dd3a3a54715@riseup.net>
2023-02-27  9:05           ` Daniel Wagner
     [not found]             ` <4a7c105b-f046-3054-a1fd-9441af48b491@riseup.net>
2023-02-28  9:54               ` Daniel Wagner

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=ed916236ae7f2823aeccc8a85230abe5@riseup.net \
    --to=fuckgithub@riseup.net \
    --cc=axboe@fb.com \
    --cc=busch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox