public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: <torvalds@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Block drivers bits for 4.1
Date: Thu, 16 Apr 2015 18:44:36 -0600	[thread overview]
Message-ID: <20150417004436.GB8573@kernel.dk> (raw)

Hi Linus,

This is the block driver pull request for 4.1. As with the core bits,
this is a relatively slow round. This pull request contains:

- Various fixes and cleanups for NVMe, from Alexey Khoroshilov, Chong
  Yuan, myself, Keith Busch, and Murali Iyer.

- Documentation and code cleanups for nbd from Markus Pargmann.

- Change of brd maintainer to me, from Ross Zwisler. At least the email
  doesn't bounce anymore then.

- Two xen-blkback fixes from Tao Chen.

Please pull!

  git://git.kernel.dk/linux-block.git for-4.1/drivers

----------------------------------------------------------------

Alexey Khoroshilov (1):
      NVMe: Fix error handling of class_create("nvme")

Chong Yuan (1):
      NVMe: embedded iod mask cleanup

David Rientjes (2):
      block, drbd: fix drbd_req_new() initialization
      block, drbd: use mempool_create_slab_pool()

Jens Axboe (2):
      NVMe: increase depth of admin queue
      Merge branch 'stable/for-jens-4.1' of git://git.kernel.org/.../konrad/xen into for-4.1/drivers

Keith Busch (5):
      NVMe: Freeze admin queue on device failure
      NVMe: Fix blk-mq hot cpu notification
      NVMe: Remove check for null
      NVMe: Add translation for block limits
      NVMe: Meta data handling through submit io ioctl

Markus Pargmann (9):
      Documentation: nbd: Reformat to allow more documentation
      Documentation: nbd: Add list of module parameters
      nbd: Remove kernel internal header
      nbd: Replace kthread_create with kthread_run
      nbd: Fix device bytesize type
      nbd: Restructure debugging prints
      nbd: Remove fixme that was already fixed
      nbd: Return error code directly
      nbd: Return error pointer directly

Murali Iyer (1):
      nvme: Fix PRP list calculation for non-4k system page size

Ross Zwisler (1):
      brd: update maintainer to be Jens Axboe

Tao Chen (2):
      xen-blkback: enlarge the array size of blkback name
      xen-blkback: define pr_fmt macro to avoid the duplication of DRV_PFX

 Documentation/blockdev/nbd.txt      |  48 +++++++----
 MAINTAINERS                         |   2 +-
 drivers/block/drbd/drbd_main.c      |   7 +-
 drivers/block/drbd/drbd_req.c       |   3 +-
 drivers/block/nbd.c                 | 140 +++++++++++++------------------
 drivers/block/nvme-core.c           | 159 +++++++++++++++---------------------
 drivers/block/nvme-scsi.c           |  28 ++++++-
 drivers/block/xen-blkback/blkback.c |  62 +++++++-------
 drivers/block/xen-blkback/common.h  |   6 --
 drivers/block/xen-blkback/xenbus.c  |  38 +++++----
 include/linux/nbd.h                 |  46 -----------
 include/linux/nvme.h                |   5 +-
 12 files changed, 242 insertions(+), 302 deletions(-)
 delete mode 100644 include/linux/nbd.h

-- 
Jens Axboe


                 reply	other threads:[~2015-04-17  0:44 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=20150417004436.GB8573@kernel.dk \
    --to=axboe@fb.com \
    --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