Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [GIT PULL] nvme fix for 4.16-rc6
Date: Fri, 16 Mar 2018 10:53:58 -0600	[thread overview]
Message-ID: <20180316165357.GD720@localhost.localdomain> (raw)
In-Reply-To: <8734416c-cd14-8bfb-8e2c-6eab84e0ce5d@kernel.dk>

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.

I understand the concern on the timing. If you can queue this
for additional testing and make a final call, that would be much
appreciated. We can copy to stable during 4.17 if you consider this too
risky for 4.16.

FWIW, this patch tests well here and even correctly aligns to Intel's
intended usage, but I'm limited to a single vendor.

  reply	other threads:[~2018-03-16 16:53 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 [this message]
2018-03-21 20:59       ` Keith Busch
2018-03-21 21:02         ` Jens Axboe
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=20180316165357.GD720@localhost.localdomain \
    --to=keith.busch@intel.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