From: <Mario.Limonciello@dell.com>
To: <sagi@grimberg.me>, <kbusch@kernel.org>
Cc: <axboe@fb.com>, <hch@lst.de>, <linux-nvme@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <Ryan.Hong@Dell.com>,
<Crag.Wang@dell.com>, <sjg@google.com>,
<Charles.Hyde@dellteam.com>, <Jared.Dominguez@dell.com>
Subject: RE: [PATCH v2] nvme: Add quirk for LiteON CL1 devices running FW 22301111
Date: Wed, 14 Aug 2019 20:19:34 +0000 [thread overview]
Message-ID: <3e38dce0c1ae406496af3a70dfd36077@AUSX13MPC105.AMER.DELL.COM> (raw)
In-Reply-To: <32f20898-b9af-eee0-97de-0a568de54b57@grimberg.me>
> -----Original Message-----
> From: Sagi Grimberg <sagi@grimberg.me>
> Sent: Wednesday, August 14, 2019 3:15 PM
> To: Limonciello, Mario; Keith Busch
> Cc: Jens Axboe; Christoph Hellwig; linux-nvme@lists.infradead.org; LKML; Hong,
> Ryan; Wang, Crag; sjg@google.com; Hyde, Charles - Dell Team; Dominguez, Jared
> Subject: Re: [PATCH v2] nvme: Add quirk for LiteON CL1 devices running FW
> 22301111
>
>
> [EXTERNAL EMAIL]
>
> Mario,
>
> Can you please respin a patch that applies cleanly on nvme-5.4?
It looks like nvme-5.4 is missing the commit coming in from Rafael's linux-next tree that it's dependent upon:
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/drivers/nvme/host?h=linux-next&id=4eaefe8c621c6195c91044396ed8060c179f7aae
Could you cherry pick that into nvme-5.4 as well? It should apply cleanly then. Otherwise, would you prefer
this to come in Rafael's tree too?
prev parent reply other threads:[~2019-08-14 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 20:08 Mario Limonciello
2019-08-14 20:08 ` Keith Busch
2019-08-14 20:14 ` Sagi Grimberg
2019-08-14 20:19 ` Keith Busch
2019-08-15 17:19 ` Sagi Grimberg
2019-08-16 19:43 ` Mario.Limonciello
2019-08-16 20:01 ` Keith Busch
2019-08-14 20:19 ` Mario.Limonciello [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=3e38dce0c1ae406496af3a70dfd36077@AUSX13MPC105.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=Charles.Hyde@dellteam.com \
--cc=Crag.Wang@dell.com \
--cc=Jared.Dominguez@dell.com \
--cc=Ryan.Hong@Dell.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=sjg@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
all inboxes | Powered by JetHome®