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] two nvme fixes for 5.0-rc3
Date: Wed, 16 Jan 2019 17:37:24 +0100 [thread overview]
Message-ID: <20190116163724.GA24217@infradead.org> (raw)
The following changes since commit 8218a55b6b911d396565da4ed5ca8b18bf0d38fb:
sbitmap: Protect swap_lock from hardirq (2019-01-14 21:30:32 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.0
for you to fetch changes up to eda14f8977df052dce3a9c54a6bf8d8f76c96eb1:
nvme-pci: fix nvme_setup_irqs() (2019-01-15 06:50:52 +0100)
----------------------------------------------------------------
Ming Lei (1):
nvme-pci: fix nvme_setup_irqs()
Sagi Grimberg (1):
nvmet-tcp: fix uninitialized variable access
drivers/nvme/host/pci.c | 21 +++++++++++++--------
drivers/nvme/target/tcp.c | 2 +-
2 files changed, 14 insertions(+), 9 deletions(-)
next reply other threads:[~2019-01-16 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 16:37 Christoph Hellwig [this message]
2019-01-16 16:45 ` [GIT PULL] two nvme fixes for 5.0-rc3 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=20190116163724.GA24217@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).