Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme fixes for Linux 4.15
Date: Fri, 5 Jan 2018 10:41:06 -0700	[thread overview]
Message-ID: <ef7ba239-5d28-9cf7-3212-1aab79a76cb0@kernel.dk> (raw)
In-Reply-To: <20180105171502.tacdqy5kh3knh4hg@infradead.org>

On 1/5/18 10:15 AM, Christoph Hellwig wrote:
> Hi Jens,
> 
> I have a few more small nvme fixes for you for Linux 4.15:
> 
> The following changes since commit 6d0e4827b72afc71349784336d5eb6df4df106e6:
> 
>   Revert "bdi: add error handle for bdi_debug_register" (2017-12-21 10:01:30 -0700)
> 
> are available in the git repository at:
> 
>   git://git.infradead.org/nvme.git nvme-4.15

Looks fine to me, pulled.

4.16 is coming up, would be nice to get at least the preliminary nvme
stuff pulled in for that.

-- 
Jens Axboe

  reply	other threads:[~2018-01-05 17:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 17:15 [GIT PULL] nvme fixes for Linux 4.15 Christoph Hellwig
2018-01-05 17:41 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-29 16:16 Christoph Hellwig
2017-11-29 16:30 ` Jens Axboe
2017-11-23 14:44 Christoph Hellwig
2017-11-24  4:54 ` Jens Axboe
2017-11-24  5:04   ` Jens Axboe
2017-11-24  8:32     ` Christoph Hellwig
2017-11-24 17:15       ` 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=ef7ba239-5d28-9cf7-3212-1aab79a76cb0@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