public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Two small fixes for 2.6.34
Date: Fri, 7 May 2010 08:58:38 +0200	[thread overview]
Message-ID: <20100507065838.GX27497@kernel.dk> (raw)
In-Reply-To: <20100507064801.GV27497@kernel.dk>

On Fri, May 07 2010, Jens Axboe wrote:
> Hi Linus,
> 
> Two small fixes for 2.6.34. One fixes a typo in drbd, and the other
> fixes a missing RCU lock in the block cgroup code. Please pull.
> 
> 
>   git://git.kernel.dk/linux-2.6-block.git for-linus
> 
> Jens Axboe (1):
>       Merge branch 'for-jens' of git://git.drbd.org/linux-2.6-drbd into for-linus
> 
> Lars Ellenberg (1):
>       drbd: don't expose failed local READ to upper layers
> 
> Vivek Goyal (1):
>       blk-cgroup: Fix RCU correctness warning in cfq_init_queue()
> 
>  block/cfq-iosched.c              |    2 ++
>  drivers/block/drbd/drbd_worker.c |    2 +-
>  2 files changed, 3 insertions(+), 1 deletions(-)

Another small RCU block cgroup fix was missed, I've pushed that out now.
New changelog/diffstat:

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

Jens Axboe (1):
      Merge branch 'for-jens' of git://git.drbd.org/linux-2.6-drbd into for-linus

Lars Ellenberg (1):
      drbd: don't expose failed local READ to upper layers

Li Zefan (1):
      blk-cgroup: Fix an RCU warning in blkiocg_create()

Vivek Goyal (1):
      blk-cgroup: Fix RCU correctness warning in cfq_init_queue()

 block/blk-cgroup.c               |    8 ++++----
 block/cfq-iosched.c              |    2 ++
 drivers/block/drbd/drbd_worker.c |    2 +-
 3 files changed, 7 insertions(+), 5 deletions(-)

-- 
Jens Axboe


      reply	other threads:[~2010-05-07  6:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07  6:48 [GIT PULL] Two small fixes for 2.6.34 Jens Axboe
2010-05-07  6:58 ` Jens Axboe [this message]

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=20100507065838.GX27497@kernel.dk \
    --to=jens.axboe@oracle.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