public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] block bits for 2.6.37-rc3
Date: Thu, 25 Nov 2010 09:07:04 +0100	[thread overview]
Message-ID: <4CEE1928.3080809@fusionio.com> (raw)

Hi Linus,

The "big" part here is the xen/blkfront transition to a
functional barrier replacement setup. Other than that,
a few fixes for build warnings/breaks, one more RCU fix
for the ioprio code, and a fix for a bug in the
blk-throttle code.

Please pull.

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

Greg Thelen (1):
      ioprio: grab rcu_read_lock in sys_ioprio_{set,get}()

Jens Axboe (2):
      Merge branch 'upstream/blkfront' of git://git.kernel.org/.../jeremy/xen into for-linus
      cciss: fix build for PROC_FS disabled

Jeremy Fitzhardinge (4):
      xen/blkfront: map REQ_FLUSH into a full barrier
      xen/blkfront: change blk_shadow.request to proper pointer
      xen/blkfront: Implement FUA with BLKIF_OP_WRITE_BARRIER
      xen/blkfront: cope with backend that fail empty BLKIF_OP_WRITE_BARRIER requests

Vivek Goyal (2):
      blk-throttle: Fix calculation of max number of WRITES to be dispatched
      block: fix amiga and atari floppy driver compile warning

 block/blk-throttle.c         |    2 +-
 drivers/block/amiflop.c      |    2 +-
 drivers/block/ataflop.c      |    2 +-
 drivers/block/cciss.c        |    3 +-
 drivers/block/xen-blkfront.c |   55 +++++++++++++++++++++++++----------------
 fs/ioprio.c                  |   31 ++++-------------------
 6 files changed, 43 insertions(+), 52 deletions(-)

-- 
Jens Axboe


                 reply	other threads:[~2010-11-25  8:07 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=4CEE1928.3080809@fusionio.com \
    --to=jaxboe@fusionio.com \
    --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