From: Jens Axboe <axboe@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 4.9-rc
Date: Fri, 21 Oct 2016 10:09:18 -0600 [thread overview]
Message-ID: <1b7e59a4-9558-801b-fe8f-0f7375d1c930@fb.com> (raw)
Hi Linus,
A set of fixes that missed the merge window, mostly due to me being away
around that time. Nothing major here, a mix of nvme cleanups and fixes,
and one fix for the badblocks handling.
Please pull!
git://git.kernel.dk/linux-block.git for-linus
----------------------------------------------------------------
Christoph Hellwig (5):
nvme.h: resync with nvme-cli
nvme.h: don't use uuid_be
nvme.h: add an enum for cns values
nvme: use symbolic constants for CNS values
nvmet: use symbolic constants for CNS values
Gabriel Krisman Bertazi (1):
nvme: Add tertiary number to NVME_VS
Keith Busch (3):
nvme: Stop probing a removed device
nvme: Delete created IO queues on reset
nvme: don't schedule multiple resets
Stephen Bates (1):
nvme : Add sysfs entry for NVMe CMBs when appropriate
Tomasz Majchrzak (1):
badblocks: fix overlapping check for clearing
block/badblocks.c | 6 ++--
drivers/nvme/host/core.c | 14 ++++----
drivers/nvme/host/pci.c | 77
+++++++++++++++++++++++++++++------------
drivers/nvme/host/scsi.c | 4 +--
drivers/nvme/target/admin-cmd.c | 8 ++---
drivers/nvme/target/core.c | 2 +-
drivers/nvme/target/discovery.c | 4 +--
include/linux/nvme.h | 49 +++++++++++++++++++++-----
8 files changed, 115 insertions(+), 49 deletions(-)
--
Jens Axboe
next reply other threads:[~2016-10-21 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 16:09 Jens Axboe [this message]
2016-10-27 16:39 [GIT PULL] Block fixes for 4.9-rc Jens Axboe
2016-11-12 0:11 Jens Axboe
2016-11-12 0:45 ` Linus Torvalds
2016-11-12 1:24 ` Jens Axboe
2016-11-17 21:36 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=1b7e59a4-9558-801b-fe8f-0f7375d1c930@fb.com \
--to=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).