All of lore.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 driver pull request for 4.2
Date: Thu, 25 Jun 2015 08:37:52 -0600	[thread overview]
Message-ID: <20150625143752.GB13739@kernel.dk> (raw)

Hi Linus,

This is the block driver pull request for 4.2. It depends on the
previously sent core pull request. This pull request contains:

- A few race fixes for null_blk, from Akinobu Mita.

- A series of fixes for mtip32xx, from Asai Thambi and Selvan Mani at
  Micron.

- NVMe:

	- Fix for missing error return on allocation failure, from Axel
	  Lin.

	- Code consolidation and cleanups from Christoph.

	- Memory barrier addition, syncing queue count and queue
	  pointers. From Jon Derrick.

	- Various fixes from Keith, an addition to support user
	  issue reset from sysfs or ioctl, and automatic namespace
	  rescan.

	- Fix from Matias, avoiding losing some request flags when
	  marking the request failfast.

- Small cleanups and sparse fixups for ps3vram. From Geert Uytterhoeven
  and Geoff Lavand.

- s390/dasd dead code removal, from Jarod Wilson.

- A set of fixes and optimizations for loop, from Ming Lei.

- Conversion to blkdev_reread_part() of loop, dasd, ndb. From Ming Lei.

- Updates to cciss. From Tomas Henzl.


Please pull!


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

----------------------------------------------------------------
Akinobu Mita (2):
      null_blk: prevent timer handler running on a different CPU where started
      null_blk: restart request processing on completion handler

Asai Thambi SP (8):
      mtip32xx: fix rmmod issue
      mtip32xx: remove unused variable 'port->allocated'
      mtip32xx: fix incorrectly setting MTIP_DDF_SEC_LOCK_BIT
      mtip32xx: Abort I/O during secure erase operation
      mtip32xx: fix crash on surprise removal of the drive
      mtip32xx: remove unnecessary sleep in mtip_ftl_rebuild_poll()
      mtip32xx: fix minor number
      mtip32xx: increase wait time for hba reset

Axel Lin (1):
      block: nvme-scsi: Catch kcalloc failure

Christoph Hellwig (10):
      nvme: disable irqs in nvme_freeze_queues
      nvme: consolidate synchronous command submission helpers
      nvme: store a struct device pointer in struct nvme_dev
      nvme: split nvme_trans_send_fw_cmd
      nvme: fix scsi translation error handling
      nvme: first round at deobsfucating the SCSI translation code
      nvme: simplify and cleanup the READ/WRITE SCSI CDB parsing code
      nvme: report the DPOFUA in MODE_SENSE
      nvme: fail SCSI read/write command with unsupported protection bit
      nvme: submit internal commands through the block layer

Geert Uytterhoeven (1):
      block/ps3vram: Remove obsolete reference to MTD

Geoff Levand (2):
      block/ps3vram: Fix sparse warnings
      MAINTAINERS: Update ps3vram block driver

Jarod Wilson (1):
      s390/block/dasd: remove obsolete while -EBUSY loop

Jens Axboe (4):
      Merge branch 'for-4.2/core' into for-4.2/drivers
      loop: remove (now) unused 'out' label
      Merge branch 'for-4.2/core' into for-4.2/drivers
      Merge branch 'for-4.2/core' into for-4.2/drivers

Jon Derrick (1):
      NVMe: Memory barrier before queue_count is incremented

Keith Busch (7):
      NVMe: Fix obtaining command result
      NVMe: Use requested sync command timeout
      NVMe: End sync requests immediately on failure
      NVMe: Remove hctx reliance for multi-namespace
      NVMe: add sysfs and ioctl controller reset
      NVMe: Automatic namespace rescan
      NVMe: Fix IO for extended metadata formats

Matias Bjørling (1):
      nvme: don't overwrite req->cmd_flags on sync cmd

Ming Lei (6):
      block: loop: convert to per-device workqueue
      block: loop: avoiding too many pending per work I/O
      block: loop: don't hold lo_ctl_mutex in lo_open
      block: loop: fix another reread part failure
      block: nbd: convert to blkdev_reread_part()
      block: dasd_genhd: convert to blkdev_reread_part

Selvan Mani (1):
      mtip32xx: Fix accessing freed memory

Tomas Henzl (2):
      cciss: remove duplicate entries from board_type struct
      cciss: correct the non-resettable board list

 MAINTAINERS                       |    2 +
 drivers/block/cciss.c             |   27 +-
 drivers/block/loop.c              |   82 ++-
 drivers/block/loop.h              |    3 +-
 drivers/block/mtip32xx/mtip32xx.c |  228 +++----
 drivers/block/mtip32xx/mtip32xx.h |   10 +-
 drivers/block/nbd.c               |    2 +-
 drivers/block/null_blk.c          |   14 +-
 drivers/block/nvme-core.c         |  809 +++++++++++++-----------
 drivers/block/nvme-scsi.c         | 1230 +++++++++++--------------------------
 drivers/block/ps3vram.c           |   34 +-
 drivers/s390/block/dasd_genhd.c   |   19 +-
 include/linux/nvme.h              |   31 +-
 include/uapi/linux/nvme.h         |    5 +
 14 files changed, 1007 insertions(+), 1489 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2015-06-25 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 14:37 Jens Axboe [this message]
2015-06-26 21:20 ` [GIT PULL] Block driver pull request for 4.2 Davidlohr Bueso
2015-06-27 17:42   ` 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=20150625143752.GB13739@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.