mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: "Jim.Lin" <jim.chihjung.lin@gmail.com>
Cc: axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	jim.lin@siliconmotion.com, cj.chen@siliconmotion.com,
	david.yeh@siliconmotion.com, hardaway.tseng@sk.com
Subject: Re: [PATCH] Merge tag: Fixed an issue where it takes more than 20 mins for SK Hynix BC901 to switch to developer mode on Chromebook
Date: Mon, 27 Nov 2023 11:16:36 -0700	[thread overview]
Message-ID: <ZWTdBKLU32mEc70A@kbusch-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20231123100642.40923-1-jim.lin@siliconmotion.com>

On Thu, Nov 23, 2023 at 06:06:42PM +0800, Jim.Lin wrote:
> SK Hynix BC901 drive write zero will cause Chromebook takes more than 20 mins to switch to developer mode
> "disable wrtie zero" can fix this issue and Sk Hynix has been verified.
> 
> Signed-off-by: Jim.Lin <jim.lin@siliconmotion.com>

For the changelog, let's abbreviate the subject to something like:

  "nvme-pci: disable write zeroes for SK Hynix BC901"

> @@ -3394,6 +3394,8 @@ static const struct pci_device_id nvme_id_table[] = {
>  		.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
>  	{ PCI_DEVICE(0x1c5c, 0x174a),   /* SK Hynix P31 SSD */
>  		.driver_data = NVME_QUIRK_BOGUS_NID, },
> +	{ PCI_DEVICE(0x1c5c, 0x1D59),   /* SK Hynix BC901 */
> +		.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },

Could we get an "Ack" from the vendor?

      reply	other threads:[~2023-11-27 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 10:06 Jim.Lin
2023-11-27 18:16 ` Keith Busch [this message]

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=ZWTdBKLU32mEc70A@kbusch-mbp.dhcp.thefacebook.com \
    --to=kbusch@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=cj.chen@siliconmotion.com \
    --cc=david.yeh@siliconmotion.com \
    --cc=hardaway.tseng@sk.com \
    --cc=hch@lst.de \
    --cc=jim.chihjung.lin@gmail.com \
    --cc=jim.lin@siliconmotion.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®