From: Jens Axboe <axboe@fb.com>
To: <torvalds@linuxfoundation.org>
Cc: <linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 4.7-rc1
Date: Fri, 27 May 2016 12:37:49 -0600 [thread overview]
Message-ID: <20160527183749.GA30050@kernel.dk> (raw)
Hi Linus,
A set of fixes that wasn't included in the first merge window pull
request. This pull request contains:
- A set of NVMe fixes from Keith, and one from Nic for the integrity
side of it.
- Fix from Ming, clearing ->mq_ops if we don't successfully setup a
queue for multiqueue.
- A set of stability fixes for bcache from Jiri, and also marking bcache
as orphaned as it's no longer actively maintained (in mainline, at
least).
Please pull!
git://git.kernel.dk/linux-block.git for-linus
----------------------------------------------------------------
Jiri Kosina (4):
bcache: bch_writeback_thread() is not freezable
bcache: bch_allocator_thread() is not freezable
bcache: bch_gc_thread() is not freezable
MAINTAINERS: mark bcache as orphan
Keith Busch (7):
NVMe: Allocate queues only for online cpus
NVMe: Delete only created queues
NVMe: Unbind driver on failure
NVMe: Reduce driver log spamming
NVMe: Allow user initiated rescan
NVMe: Short-cut removal on surprise hot-unplug
NVMe: Add device ID's with stripe quirk
Ming Lin (1):
blk-mq: clear q->mq_ops if init fail
Nicholas Bellinger (1):
nvme/host: Add missing blk_integrity tag_size + flags assignments
MAINTAINERS | 2 +-
block/blk-mq.c | 4 +++-
drivers/md/bcache/alloc.c | 2 --
drivers/md/bcache/btree.c | 2 --
drivers/md/bcache/writeback.c | 3 ---
drivers/nvme/host/core.c | 37 +++++++++++++++++++++++++++++++++++++
drivers/nvme/host/nvme.h | 1 +
drivers/nvme/host/pci.c | 23 ++++++++++++++++++-----
include/uapi/linux/nvme_ioctl.h | 1 +
9 files changed, 61 insertions(+), 14 deletions(-)
--
Jens Axboe
reply other threads:[~2016-05-27 18:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160527183749.GA30050@kernel.dk \
--to=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linuxfoundation.org \
/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).