All of lore.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: Re: [GIT PULL] fix for loop warning
Date: Thu, 28 Oct 2010 07:32:36 -0600	[thread overview]
Message-ID: <4CC97B74.3000808@fusionio.com> (raw)
In-Reply-To: <AANLkTink4hKJk_-Pb-rPxQcBH5WcBKqf=9ybZ7thL1O6@mail.gmail.com>

On 2010-10-27 19:47, Linus Torvalds wrote:
> On Tue, Oct 26, 2010 at 9:18 PM, Jens Axboe <jaxboe@fusionio.com> wrote:
>>
>>  git://git.kernel.dk/linux-2.6-block.git for-linus
> 
> "Already up-to-date."
> 
> Forgot to push?

Must have... The branch has now been updated with a few other pending
patches. All pretty trivial and straight forward changes.

Please pull (again :-).


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

Andrew Morton (1):
      drivers/block/aoe/aoeblk.c: ratelimit a warning printk

Geert Uytterhoeven (1):
      drivers/block/z2ram.c: correct printing of sector_t

Mike Miller (1):
      cciss: remove overlapping PCI IDs

Milan Broz (1):
      loop: Properly clear sysfs in autoclear mode

Nicolas Kaiser (1):
      drivers/block/drbd/drbd_main.c: fix error path

Tejun Heo (1):
      aoe: don't use flush_scheduled_work()

Vasiliy Kulikov (1):
      block: cciss: fix information leak to userland

 drivers/block/aoe/aoeblk.c     |    4 +++-
 drivers/block/aoe/aoedev.c     |    4 +---
 drivers/block/cciss.c          |   37 +------------------------------------
 drivers/block/drbd/drbd_main.c |    2 +-
 drivers/block/loop.c           |    2 +-
 drivers/block/z2ram.c          |    6 ++++--
 6 files changed, 11 insertions(+), 44 deletions(-)


-- 
Jens Axboe


  reply	other threads:[~2010-10-28 13:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27  4:18 [GIT PULL] fix for loop warning Jens Axboe
2010-10-28  1:47 ` Linus Torvalds
2010-10-28 13:32   ` Jens Axboe [this message]
2010-10-28 11:38 ` Christoph Hellwig

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=4CC97B74.3000808@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 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.