From: Keith Busch <kbusch@kernel.org>
To: "Mario.Limonciello@dell.com" <Mario.Limonciello@dell.com>
Cc: "sagi@grimberg.me" <sagi@grimberg.me>,
"axboe@fb.com" <axboe@fb.com>, "hch@lst.de" <hch@lst.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Ryan.Hong@Dell.com" <Ryan.Hong@Dell.com>,
"Crag.Wang@dell.com" <Crag.Wang@dell.com>,
"sjg@google.com" <sjg@google.com>,
"Charles.Hyde@dellteam.com" <Charles.Hyde@dellteam.com>,
"Jared.Dominguez@dell.com" <Jared.Dominguez@dell.com>
Subject: Re: [PATCH v2] nvme: Add quirk for LiteON CL1 devices running FW 22301111
Date: Fri, 16 Aug 2019 14:01:26 -0600 [thread overview]
Message-ID: <20190816200125.GB6883@localhost.localdomain> (raw)
In-Reply-To: <d71fc97ef6c8428f96ecfb2cec6077ab@AUSX13MPC101.AMER.DELL.COM>
On Fri, Aug 16, 2019 at 12:43:02PM -0700, Mario.Limonciello@dell.com wrote:
> > 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.
>
> The dependent commit is in Linus' tree now.
> 4eaefe8c621c6195c91044396ed8060c179f7aae
>
> Also it was reported to me after this was submitted that the comment
> whitespace should have been aligned during the switchover from v1 to v2.
>
> V1 the whitespace was further left since it was applying to 3 drives, but now
> that they're combined in v2 the whitespace wasn't adjusted.
>
> Let me know if you want me to resubmit v3 w/ whitespace modification or
> if you will want to adjust that locally when you pull it in.
Go ahead and resend the patch with your fixes included. This is going to
have to wait till next week anyway in order to have a clean pull request
through our normal path to mainline.
next prev parent reply other threads:[~2019-08-16 20:04 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
2019-08-16 19:43 ` Mario.Limonciello
2019-08-16 20:01 ` Keith Busch [this message]
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=20190816200125.GB6883@localhost.localdomain \
--to=kbusch@kernel.org \
--cc=Charles.Hyde@dellteam.com \
--cc=Crag.Wang@dell.com \
--cc=Jared.Dominguez@dell.com \
--cc=Mario.Limonciello@dell.com \
--cc=Ryan.Hong@Dell.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).