Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Pascal Terjan <pterjan@google.com>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: Add quirks for Lexar 256GB SSD
Date: Wed, 24 Feb 2021 09:21:47 +0000	[thread overview]
Message-ID: <20210224092147.GA2195892@infradead.org> (raw)
In-Reply-To: <20210223221046.3367795-1-pterjan@google.com>

On Tue, Feb 23, 2021 at 10:10:46PM +0000, Pascal Terjan wrote:
> Add NVME_QUIRK_NO_NS_DESC_LIST to Lexar 256GB SSD to allow it to
> work again, and add NVME_QUIRK_IGNORE_DEV_SUBNQN to avoid a warning.

Why again?  The drive has always been broken since the desc list has
been a mandatory feature since NVMe 1.3..

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  parent reply	other threads:[~2021-02-24  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 22:10 [PATCH] nvme: Add quirks for Lexar 256GB SSD Pascal Terjan
2021-02-24  7:21 ` Chaitanya Kulkarni
2021-02-24  9:21 ` Christoph Hellwig [this message]
2021-02-24 10:23   ` Pascal Terjan
2021-02-25 16:22     ` Keith Busch

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=20210224092147.GA2195892@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=pterjan@google.com \
    /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