Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme fix for 4.16-rc6
Date: Wed, 21 Mar 2018 15:02:06 -0600	[thread overview]
Message-ID: <dc2798b4-5654-9fc3-444e-efbce5775ca4@kernel.dk> (raw)
In-Reply-To: <20180321205958.GH12909@localhost.localdomain>

On 3/21/18 2:59 PM, Keith Busch wrote:
> On Fri, Mar 16, 2018@09:26:24AM -0700, Jens Axboe wrote:
>> It's not that I dislike the patch (in fact it makes the code
>> easier to read), but it's pretty late for something that isn't
>> a regression in this series. I can queue it up for some testing,
>> but it's then -rc7 time. I guess we can see how it goes and
>> push the decision until start next week.
> 
> Hi Jens,
> 
> Do you need more time on this one or have you decided where you want
> this fix to go? I'm planning to send the first nvme 4.17 pull request
> this week, so just checking if I should include this one.

Let's ship it for 4.16.

-- 
Jens Axboe

  reply	other threads:[~2018-03-21 21:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 16:01 [GIT PULL] nvme fix for 4.16-rc6 Keith Busch
2018-03-16 16:14 ` Jens Axboe
2018-03-16 16:16   ` Christoph Hellwig
2018-03-16 16:26     ` Jens Axboe
2018-03-16 16:53       ` Keith Busch
2018-03-21 20:59       ` Keith Busch
2018-03-21 21:02         ` Jens Axboe [this message]
2018-03-21 21:44           ` Jens Axboe
2018-03-21 22:08             ` Keith Busch
2018-03-22 21:09             ` Keith Busch
2018-03-22 21:32               ` Jens Axboe
2018-03-22 22:02                 ` Keith Busch
2018-03-22 22:09                   ` Jens Axboe

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=dc2798b4-5654-9fc3-444e-efbce5775ca4@kernel.dk \
    --to=axboe@kernel.dk \
    /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