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 fix for 5.0
Date: Wed, 13 Feb 2019 08:04:38 +0100 [thread overview]
Message-ID: <20190213070438.GA11528@infradead.org> (raw)
The following changes since commit aef1897cd36dcf5e296f1d2bae7e0d268561b685:
blk-mq: insert rq with DONTPREP to hctx dispatch list when requeue (2019-02-11 19:51:52 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.0
for you to fetch changes up to 4726bcf30fad37cc555cd9dcd6c73f2b2668c879:
nvme-pci: add missing unlock for reset error (2019-02-12 09:29:07 +0100)
----------------------------------------------------------------
Keith Busch (1):
nvme-pci: add missing unlock for reset error
drivers/nvme/host/pci.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
next reply other threads:[~2019-02-13 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 7:04 Christoph Hellwig [this message]
2019-02-13 14:32 ` [GIT PULL] nvme fix for 5.0 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=20190213070438.GA11528@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).