All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <keith.busch@intel.com>,
	linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for 5.0
Date: Wed, 6 Feb 2019 16:38:28 +0100	[thread overview]
Message-ID: <20190206153828.GA14994@infradead.org> (raw)

The following changes since commit ec51f8ee1e63498e9f521ec0e5a6d04622bb2c67:

  aio: initialize kiocb private in case any filesystems expect it. (2019-02-06 08:04:22 -0700)

are available in the Git repository at:

  git://git.infradead.org/nvme.git nvme-5.0

for you to fetch changes up to 5c959d73dba6495ec01d04c206ee679d61ccb2b0:

  nvme-pci: fix rapid add remove sequence (2019-02-06 16:35:33 +0100)

----------------------------------------------------------------
Keith Busch (2):
      nvme: lock NS list changes while handling command effects
      nvme-pci: fix rapid add remove sequence

 drivers/nvme/host/core.c |  8 +++++++-
 drivers/nvme/host/nvme.h |  1 +
 drivers/nvme/host/pci.c  | 22 ++++++++++++----------
 3 files changed, 20 insertions(+), 11 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: hch@infradead.org (Christoph Hellwig)
Subject: [GIT PULL] nvme fixes for 5.0
Date: Wed, 6 Feb 2019 16:38:28 +0100	[thread overview]
Message-ID: <20190206153828.GA14994@infradead.org> (raw)

The following changes since commit ec51f8ee1e63498e9f521ec0e5a6d04622bb2c67:

  aio: initialize kiocb private in case any filesystems expect it. (2019-02-06 08:04:22 -0700)

are available in the Git repository at:

  git://git.infradead.org/nvme.git nvme-5.0

for you to fetch changes up to 5c959d73dba6495ec01d04c206ee679d61ccb2b0:

  nvme-pci: fix rapid add remove sequence (2019-02-06 16:35:33 +0100)

----------------------------------------------------------------
Keith Busch (2):
      nvme: lock NS list changes while handling command effects
      nvme-pci: fix rapid add remove sequence

 drivers/nvme/host/core.c |  8 +++++++-
 drivers/nvme/host/nvme.h |  1 +
 drivers/nvme/host/pci.c  | 22 ++++++++++++----------
 3 files changed, 20 insertions(+), 11 deletions(-)

             reply	other threads:[~2019-02-06 15:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 15:38 Christoph Hellwig [this message]
2019-02-06 15:38 ` [GIT PULL] nvme fixes for 5.0 Christoph Hellwig
2019-02-06 15:46 ` Jens Axboe
2019-02-06 15:46   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2019-01-10 17:09 Christoph Hellwig
2019-01-10 17:09 ` Christoph Hellwig

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=20190206153828.GA14994@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.