linux-block.vger.kernel.org archive mirror
 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 4.19
Date: Wed, 29 Aug 2018 18:51:14 +0200	[thread overview]
Message-ID: <20180829165114.GA15464@infradead.org> (raw)

The following changes since commit db193954ed9e35701b6e489fa4cc97b08589341b:

  block: bsg: move atomic_t ref_count variable to refcount API (2018-08-27 19:17:02 -0600)

are available in the Git repository at:

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

for you to fetch changes up to 04db0e5ec58167364a80fd33ddb4f3b67434eb85:

  nvmet: free workqueue object if module init fails (2018-08-28 08:40:44 +0200)

----------------------------------------------------------------
Chaitanya Kulkarni (1):
      nvmet: free workqueue object if module init fails

James Smart (1):
      nvme-fcloop: Fix dropped LS's to removed target port

Michal Wnukowski (1):
      nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

 drivers/nvme/host/pci.c      | 8 ++++++++
 drivers/nvme/target/core.c   | 4 +++-
 drivers/nvme/target/fcloop.c | 3 ++-
 3 files changed, 13 insertions(+), 2 deletions(-)

             reply	other threads:[~2018-08-29 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 16:51 Christoph Hellwig [this message]
2018-08-29 17:05 ` [GIT PULL] nvme fixes for 4.19 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2018-09-28 15:40 Christoph Hellwig
2018-09-28 15:42 ` 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=20180829165114.GA15464@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 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).