linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <keith.busch@intel.com>,
	linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for 5.2
Date: Thu, 16 May 2019 08:09:30 -0600	[thread overview]
Message-ID: <a2c12d06-acd0-ea82-c63c-a068ec5ae1fe@kernel.dk> (raw)
In-Reply-To: <20190516082541.GA19383@infradead.org>

On 5/16/19 2:25 AM, Christoph Hellwig wrote:
> The following changes since commit 936b33f7243fa1e54c8f4f2febd3472cc00e66fd:
> 
>   brd: add cond_resched to brd_free_pages (2019-05-09 12:51:27 -0600)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git nvme-5.2
> 
> for you to fetch changes up to 1b1031ca63b2ce1d3b664b35b77ec94e458693e9:
> 
>   nvme: validate cntlid during controller initialisation (2019-05-14 17:19:50 +0200)
> 
> ----------------------------------------------------------------
> Chaitanya Kulkarni (1):
>       nvme: trace all async notice events
> 
> Christoph Hellwig (2):
>       nvme: change locking for the per-subsystem controller list
>       nvme: validate cntlid during controller initialisation
> 
> Gustavo A. R. Silva (1):
>       nvme-pci: mark expected switch fall-through
> 
> Hannes Reinecke (2):
>       nvme-fc: use separate work queue to avoid warning
>       nvme-multipath: avoid crash on invalid subsystem cntlid enumeration
> 
> Max Gurtovoy (1):
>       nvme-rdma: remove redundant reference between ib_device and tagset
> 
> Maxim Levitsky (2):
>       nvme-pci: init shadow doorbell after each reset
>       nvme-pci: add known admin effects to augument admin effects log page
> 
> Minwoo Im (2):
>       nvme-fabrics: remove unused argument
>       nvme: fix typos in nvme status code values
> 
>  drivers/nvme/host/core.c      | 79 ++++++++++++++++++++++---------------------
>  drivers/nvme/host/fabrics.c   |  4 +--
>  drivers/nvme/host/fc.c        | 14 ++++++--
>  drivers/nvme/host/multipath.c |  2 +-
>  drivers/nvme/host/pci.c       |  4 +--
>  drivers/nvme/host/rdma.c      | 34 +++----------------
>  drivers/nvme/host/trace.h     |  1 +
>  include/linux/nvme.h          |  4 +--
>  8 files changed, 64 insertions(+), 78 deletions(-)

Pulled, thanks.

-- 
Jens Axboe


      reply	other threads:[~2019-05-16 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16  8:25 [GIT PULL] nvme fixes for 5.2 Christoph Hellwig
2019-05-16 14:09 ` 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=a2c12d06-acd0-ea82-c63c-a068ec5ae1fe@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=keith.busch@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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;
as well as URLs for NNTP newsgroup(s).