From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail•com>
Cc: Jens Axboe <jens.axboe@oracle•com>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Ingo Molnar <mingo@elte•hu>,
dm-devel@redhat•com, Tejun Heo <tj@kernel•org>
Subject: Re: linux-next: Tree for August 27
Date: Fri, 29 Aug 2008 18:36:42 +1000 [thread overview]
Message-ID: <20080829183642.6994f4dc.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080829070515.GL20055@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
Hi Bart,
On Fri, 29 Aug 2008 09:05:16 +0200 Jens Axboe <jens.axboe@oracle•com> wrote:
>
> On Fri, Aug 29 2008, Bartlomiej Zolnierkiewicz wrote:
> >
> > From: Bartlomiej Zolnierkiewicz <bzolnier@gmail•com>
> > Subject: [PATCH] block: fix part0 handling in bdget_disk() / blk_lookup_devt()
> >
> > part0 is a "special" partition and doesn't need to have capacity set - this
> > fixes regression caused by "block: move __dev from disk to part0" commit.
> >
> > Cc: Tejun Heo <tj@kernel•org>
> > Cc: Jens Axboe <jens.axboe@oracle•com>
> > Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail•com>
> > ---
> > Jens, please integrate it into the original commit if feasible.
>
> Thanks Bart, I folded it into the original commit.
And applied to today's linux-next.
> > On the somehow related topic - CONFIG_DEBUG_BLOCK_EXT_DEVT which is
> > introduced by commit 3e5ba59bbab878f60b8b87004ac55a464bddc819 ("block:
> > implement CONFIG_DEBUG_BLOCK_EXT_DEVT") is way too intrusive to be
> > enabled by default if CONFIG_DEBUG_KERNEL is set as it easily results
> > in no longer bootable systems (+ help entry for the new option says
> > "Say N if you are unsure.").
> >
> > Tejun/Jens: please consider changing this.
>
> I have change the default to 'n' for now.
I will do this for today as well.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-29 8:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 8:34 linux-next: Tree for August 27 Stephen Rothwell
2008-08-27 10:06 ` Bartlomiej Zolnierkiewicz
2008-08-27 14:57 ` Bartlomiej Zolnierkiewicz
2008-08-27 19:45 ` Bartlomiej Zolnierkiewicz
2008-08-29 0:10 ` Bartlomiej Zolnierkiewicz
2008-08-29 7:05 ` Jens Axboe
2008-08-29 8:36 ` Stephen Rothwell [this message]
2008-08-29 9:35 ` [PATCH] block: don't test for partition size in bdget_disk() and blk_lookup_devt() Tejun Heo
2008-08-29 9:37 ` linux-next: Tree for August 27 Tejun Heo
2008-08-29 9:42 ` Jens Axboe
2008-08-29 19:23 ` Bartlomiej Zolnierkiewicz
2008-08-30 9:10 ` Tejun Heo
2008-08-31 13:38 ` Bartlomiej Zolnierkiewicz
2008-09-01 11:00 ` [PATCH #blk-for-2.8] init: DEBUG_BLOCK_EXT_DEVT requires explicit root= param Tejun Heo
2008-09-01 11:16 ` Jens Axboe
2008-09-01 11:20 ` Tejun Heo
2008-09-01 11:30 ` Jens Axboe
2008-09-01 11:38 ` Tejun Heo
2008-09-01 16:34 ` Bartlomiej Zolnierkiewicz
2008-08-28 1:25 ` linux-next: Tree for August 27 Stephen Rothwell
2008-08-28 9:08 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2010-08-27 2:12 Stephen Rothwell
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=20080829183642.6994f4dc.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bzolnier@gmail$(echo .)com \
--cc=dm-devel@redhat$(echo .)com \
--cc=jens.axboe@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=tj@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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