From: Sagi Grimberg <sagi@grimberg.me>
To: Keith Busch <kbusch@kernel.org>
Cc: Mario Limonciello <mario.limonciello@dell.com>,
Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ryan Hong <Ryan.Hong@Dell.com>, Crag Wang <Crag.Wang@dell.com>,
"sjg@google.com" <sjg@google.com>,
Charles Hyde <charles.hyde@dellteam.com>,
Jared Dominguez <jared.dominguez@dell.com>
Subject: Re: [PATCH v2] nvme: Add quirk for LiteON CL1 devices running FW 22301111
Date: Thu, 15 Aug 2019 10:19:04 -0700 [thread overview]
Message-ID: <0cafca37-011d-4c19-4462-14687046a153@grimberg.me> (raw)
In-Reply-To: <20190814201900.GA3511@localhost.localdomain>
>> Mario,
>>
>> Can you please respin a patch that applies cleanly on nvme-5.4?
>
> This fixes a regression we introduced in 5.3, so it should go in
> 5.3-rc. For this to apply cleanly, though, we'll need to resync to Linus'
> tree to get Rafael's PCIe ASPM check after he sends his linux-pm pull
> request.
We need to coordinate with Jens, don't think its a good idea if I'll
just randomly get stuff from linus' tree and send an rc pull request.
next prev parent reply other threads:[~2019-08-15 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 20:08 [PATCH v2] nvme: Add quirk for LiteON CL1 devices running FW 22301111 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 [this message]
2019-08-16 19:43 ` Mario.Limonciello
2019-08-16 20:01 ` Keith Busch
2019-08-14 20:19 ` Mario.Limonciello
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=0cafca37-011d-4c19-4462-14687046a153@grimberg.me \
--to=sagi@grimberg.me \
--cc=Crag.Wang@dell.com \
--cc=Ryan.Hong@Dell.com \
--cc=axboe@fb.com \
--cc=charles.hyde@dellteam.com \
--cc=hch@lst.de \
--cc=jared.dominguez@dell.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mario.limonciello@dell.com \
--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;
as well as URLs for NNTP newsgroup(s).