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] Followup block pull request for 3.20-rc1
Date: Sat, 21 Feb 2015 12:20:10 -0800	[thread overview]
Message-ID: <20150221202010.GA8092@kernel.dk> (raw)

Hi Linus,

Two things in this pull request:

- A block throttle oops fix (marked for stable) from Thadeu.

- The NVMe fixes/features queued up for 3.20, but merged later in the
  process. From Keith. We should have gotten this merged earlier, we're
  ironing out the kinks in the process. Will be ready for the initial
  pull next series.

Please pull!

  git://git.kernel.dk/linux-block.git for-linus

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

Jens Axboe (1):
      Merge branch 'for-3.20' of git://git.infradead.org/users/kbusch/linux-nvme into for-linus

Keith Busch (8):
      NVMe: Metadata format support
      NVMe: Update SCSI Inquiry VPD 83h translation
      NVMe: Register management handle under nvme class
      NVMe: Asynchronous controller probe
      NVMe: Fix potential corruption during shutdown
      NVMe: Fix scsi mode select llbaa setting
      NVMe: Remove unused variables
      NVMe: Fix potential corruption on sync commands

Thadeu Lima de Souza Cascardo (1):
      blk-throttle: check stats_cpu before reading it from sysfs

 block/blk-throttle.c      |   3 +
 drivers/block/nvme-core.c | 496 +++++++++++++++++++++++++++++++---------------
 drivers/block/nvme-scsi.c |  96 +++++----
 include/linux/nvme.h      |   9 +-
 include/uapi/linux/nvme.h |  26 ++-
 5 files changed, 417 insertions(+), 213 deletions(-)

-- 
Jens Axboe


                 reply	other threads:[~2015-02-21 20:20 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=20150221202010.GA8092@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