Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme fixes for 4.18
Date: Thu, 26 Jul 2018 10:49:25 -0700	[thread overview]
Message-ID: <a98e6d60-68ff-c044-2b68-364d1e3a3aed@kernel.dk> (raw)
In-Reply-To: <20180726141640.GA7156@infradead.org>

On 7/26/18 7:16 AM, Christoph Hellwig wrote:
> Two small fixes each for the FC code and the target.
> 
> 
> The following changes since commit 8f3ea35929a0806ad1397db99a89ffee0140822a:
> 
>   nbd: handle unexpected replies better (2018-07-16 10:14:40 -0600)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git nvme-4.18
> 
> for you to fetch changes up to 405a7519607e7a364114896264440c0f87b325c0:
> 
>   nvmet: only check for filebacking on -ENOTBLK (2018-07-25 13:14:04 +0200)
> 
> ----------------------------------------------------------------
> Hannes Reinecke (2):
>       nvmet: fixup crash on NULL device path
>       nvmet: only check for filebacking on -ENOTBLK
> 
> James Smart (2):
>       nvmet-fc: fix target sgl list on large transfers
>       nvme: if_ready checks to fail io to deleting controller

Pulled, thanks.

-- 
Jens Axboe

  reply	other threads:[~2018-07-26 17:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 14:16 [GIT PULL] nvme fixes for 4.18 Christoph Hellwig
2018-07-26 17:49 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-22 13:00 Christoph Hellwig
2018-06-22 14:46 ` Jens Axboe
2018-06-15 13:13 Christoph Hellwig
2018-06-15 14:16 ` Jens Axboe
2018-06-08  5:58 Christoph Hellwig
2018-06-08 13:09 ` Jens Axboe
2018-06-08 18:51   ` 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=a98e6d60-68ff-c044-2b68-364d1e3a3aed@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