Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme fixes for 5.2-rc2
Date: Thu, 23 May 2019 10:27:30 -0600	[thread overview]
Message-ID: <8ff0f44c-ce49-e39f-aa45-e45ff8e5efb0@kernel.dk> (raw)
In-Reply-To: <20190523161423.GD14943@localhost.localdomain>

On 5/23/19 10:14 AM, Keith Busch wrote:
> Mostly fixes we'd like included ahead of the next rc.
> 
> The only non-fix is an update to the MAINTAINERS file to point to my
> kernel.org account. This is preferred to receive communication as most
> nvme development/maintenance is on my own time anyway. I will also be
> starting extended vacation after tomorrow, but would like to still keep
> a finger on the nvme pulse.
> 
> The following changes since commit a6a4b66bd8f41922c543f7a820c66ed59c25995e:
> 
>    Merge tag 'for-linus-20190516' of git://git.kernel.dk/linux-block (2019-05-16 19:10:37 -0700)
> 
> are available in the Git repository at:
> 
>    git://git.infradead.org/nvme.git nvme-5.2-rc2
> 
> for you to fetch changes up to cb9e0e5006064a807b5d722c7e3c42f307193792:
> 
>    nvme-pci: use blk-mq mapping for unmanaged irqs (2019-05-22 10:11:36 -0600)
> 
> ----------------------------------------------------------------
> Christoph Hellwig (4):
>        nvme: fix srcu locking on error return in nvme_get_ns_from_disk
>        nvme: remove the ifdef around nvme_nvm_ioctl
>        nvme: merge nvme_ns_ioctl into nvme_ioctl
>        nvme: release namespace SRCU protection before performing controller ioctls
> 
> Keith Busch (7):
>        nvme-pci: Fix controller freeze wait disabling
>        nvme-pci: Don't disable on timeout in reset state
>        nvme-pci: Unblock reset_work on IO failure
>        nvme-pci: Sync queues on reset
>        nvme: Fix known effects
>        nvme: update MAINTAINERS
>        nvme-pci: use blk-mq mapping for unmanaged irqs
> 
> Laine Walker-Avina (1):
>        nvme: copy MTFA field from identify controller
> 
> Yufen Yu (1):
>        nvme: fix memory leak for power latency tolerance
> 
>   MAINTAINERS              |  2 +-
>   drivers/nvme/host/core.c | 89 +++++++++++++++++++++++++++++++++---------------
>   drivers/nvme/host/nvme.h |  1 +
>   drivers/nvme/host/pci.c  | 27 ++++++++-------
>   4 files changed, 77 insertions(+), 42 deletions(-)

Pulled, thanks Keith.

-- 
Jens Axboe

      reply	other threads:[~2019-05-23 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 16:14 [GIT PULL] nvme fixes for 5.2-rc2 Keith Busch
2019-05-23 16:27 ` Jens Axboe [this message]

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=8ff0f44c-ce49-e39f-aa45-e45ff8e5efb0@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