From: Jens Axboe <axboe@fb.com>
To: Wenbo Wang <mail_weber_wang@163.com>, <keith.busch@intel.com>
Cc: <linux-nvme@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
"Wenbo Wang" <wenbo.wang@memblaze.com>
Subject: Re: [PATCH] nvme/quirk: Add a delay before checking device ready for memblaze device
Date: Thu, 8 Sep 2016 10:18:04 -0600 [thread overview]
Message-ID: <5ec7070e-a3d5-ba90-fedf-cb707d4655d5@fb.com> (raw)
In-Reply-To: <1473351131-11811-1-git-send-email-mail_weber_wang@163.com>
On 09/08/2016 10:12 AM, Wenbo Wang wrote:
> From: Wenbo Wang <wenbo.wang@memblaze.com>
>
> Signed-off-by: Wenbo Wang <wenbo.wang@memblaze.com>
> ---
> drivers/nvme/host/pci.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> index 663c40c..2fec23c 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/drivers/nvme/host/pci.c
> @@ -2141,6 +2141,8 @@ static const struct pci_device_id nvme_id_table[] = {
> .driver_data = NVME_QUIRK_IDENTIFY_CNS, },
> { PCI_DEVICE(0x1c58, 0x0003), /* HGST adapter */
> .driver_data = NVME_QUIRK_DELAY_BEFORE_CHK_RDY, },
> + { PCI_DEVICE(0x1c5f, 0x0540), /* Memblaze Pblaze4 adapter */
> + .driver_data = NVME_QUIRK_DELAY_BEFORE_CHK_RDY, },
> { PCI_DEVICE_CLASS(PCI_CLASS_STORAGE_EXPRESS, 0xffffff) },
> { PCI_DEVICE(PCI_VENDOR_ID_APPLE, 0x2001) },
> { 0, }
Thanks, applied for 4.8.
--
Jens Axboe
next prev parent reply other threads:[~2016-09-08 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 16:12 [PATCH] nvme/quirk: Add a delay before checking device ready for memblaze device Wenbo Wang
2016-09-08 16:18 ` Jens Axboe [this message]
[not found] <CAAZN+A3m4z0uOUBWyonpXb2fQTuFhV3vu68Kuy4mdQYwt6WDgA@mail.gmail.com>
2016-09-08 14:36 ` Keith Busch
2016-09-08 14:30 ` Jens Axboe
2016-09-08 15:02 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2016-08-15 5:21 Wenbo Wang
2016-08-15 15:05 ` Keith Busch
2016-08-09 3:18 Wenbo Wang
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=5ec7070e-a3d5-ba90-fedf-cb707d4655d5@fb.com \
--to=axboe@fb.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mail_weber_wang@163.com \
--cc=wenbo.wang@memblaze.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