All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] block bits for 2.6.30-rc3
Date: Thu, 23 Apr 2009 07:14:04 -0400	[thread overview]
Message-ID: <49F04D7C.2040807@garzik.org> (raw)
In-Reply-To: <20090423103523.GT4593@kernel.dk>

Jens Axboe wrote:
> Bartlomiej Zolnierkiewicz (1):
>       block: enable by default support for large devices and files on 32-bit archs

Although I strongly support this change -- is this really appropriate 
for -rc3?

I know it's only a one-line Kconfig change, but still...  this does not 
seem to fall into the category of "regression fix."

	Jeff



  reply	other threads:[~2009-04-23 11:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 10:35 [GIT PULL] block bits for 2.6.30-rc3 Jens Axboe
2009-04-23 11:14 ` Jeff Garzik [this message]
2009-04-23 11:39   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2009-04-22 12:03 Jens Axboe
2009-04-22 12:31 ` Damien Wyart
2009-04-22 12:40   ` Jens Axboe
2009-04-22 12:47     ` 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=49F04D7C.2040807@garzik.org \
    --to=jeff@garzik.org \
    --cc=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 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.