linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "hch@infradead.org" <hch@infradead.org>,
	"kbusch@kernel.org" <kbusch@kernel.org>,
	Gopal Tiwari <gtiwari@redhat.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvme-pci: prevent SK Hynix PE8000 from using Write Zeroes command
Date: Thu, 11 Feb 2021 18:11:19 +0000	[thread overview]
Message-ID: <BYAPR04MB4965C95C3F826D7222EB3176868C9@BYAPR04MB4965.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20210211070748.GA13852@lst.de

On 2/10/21 11:07 PM, Christoph Hellwig wrote:
>>> I'd also love to retest most Write Zeroes quirks with that in place.
>> Do you prefer some variant of the following patch (totally untested)? OR
>> something else ?
> Somwhat.  As said I suspect defaulting to MDTS with a big fat comment
> might make most sense unless the new WZSL is set.
>
Okay, will send out patche(s) soon.

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

  reply	other threads:[~2021-02-11 18:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09  4:59 [PATCH] nvme-pci: prevent SK Hynix PE8000 from using Write Zeroes command Gopal Tiwari
2021-02-09  5:38 ` Chaitanya Kulkarni
2021-02-09  5:59   ` Gopal Tiwari
2021-02-10 10:12 ` Christoph Hellwig
2021-02-10 11:17   ` Gopal Tiwari
2021-02-10 13:15     ` Christoph Hellwig
2021-02-10 22:11       ` Chaitanya Kulkarni
2021-02-11  7:07         ` Christoph Hellwig
2021-02-11 18:11           ` Chaitanya Kulkarni [this message]
2021-02-24  9:13             ` Christoph Hellwig
2021-02-25  2:09               ` Chaitanya Kulkarni
2021-02-25  7:56                 ` Gopal Tiwari

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=BYAPR04MB4965C95C3F826D7222EB3176868C9@BYAPR04MB4965.namprd04.prod.outlook.com \
    --to=chaitanya.kulkarni@wdc.com \
    --cc=gtiwari@redhat.com \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).