From: Wu Fengguang <wfg@mail.ustc.edu.cn>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-mm3: no help text for READAHEAD_ALLOW_OVERHEADS
Date: Tue, 27 Jun 2006 23:52:27 +0800 [thread overview]
Message-ID: <351423538.03814@ustc.edu.cn> (raw)
Message-ID: <20060627155227.GA6014@mail.ustc.edu.cn> (raw)
In-Reply-To: <20060627144019.GA13915@stusta.de>
On Tue, Jun 27, 2006 at 04:40:19PM +0200, Adrian Bunk wrote:
> On Tue, Jun 27, 2006 at 09:43:37PM +0800, Wu Fengguang wrote:
> > On Tue, Jun 27, 2006 at 11:14:29AM +0200, Adrian Bunk wrote:
> > > On Tue, Jun 27, 2006 at 01:52:11AM -0700, Andrew Morton wrote:
> > > >...
> > > > Changes since 2.6.17-mm2:
> > > > +readahead-kconfig-option-readahead_allow_overheads.patch
> > > >...
> > > > readahead updates
> > > >...
> > >
> > > The READAHEAD_ALLOW_OVERHEADS option lacks a help text.
> >
> > Oh, it just acts as a submenu and a reminder ;)
> >
> > > Additionally, the "default n" is pointless and should be removed.
> >
> > I expect the _extra_ features are useless for normal users.
> > Your reasoning or feeling?
> >...
>
> That's not my point, my point is that if you remove the "default n"
> line, nothing changes. The default is still "n", but it's better
> readable.
Sorry, I didn't know that. Thanks.
Wu
next prev parent reply other threads:[~2006-06-27 15:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 8:52 2.6.17-mm3 Andrew Morton
2006-06-27 9:14 ` 2.6.17-mm3: no help text for READAHEAD_ALLOW_OVERHEADS Adrian Bunk
[not found] ` <20060627134337.GA6117@mail.ustc.edu.cn>
2006-06-27 13:43 ` Wu Fengguang
2006-06-27 14:40 ` Adrian Bunk
[not found] ` <20060627155227.GA6014@mail.ustc.edu.cn>
2006-06-27 15:52 ` Wu Fengguang [this message]
2006-06-27 17:46 ` Randy.Dunlap
2006-06-27 17:55 ` Adrian Bunk
2006-06-27 9:28 ` [patch] irq: fix arch/i386/kernel/irq.c gcc warning Ingo Molnar
2006-06-27 11:06 ` Björn Steinbrink
2006-06-27 11:14 ` x86_64-mm-ieee1394-early.patch (was Re: 2.6.17-mm3) Stefan Richter
2006-06-27 11:17 ` 2.6.17-mm3 Reuben Farrelly
2006-06-27 11:48 ` 2.6.17-mm3 Reuben Farrelly
2006-06-27 14:12 ` 2.6.17-mm3 Michal Piotrowski
2006-06-27 21:38 ` 2.6.17-mm3 Steve Fox
2006-06-27 23:12 ` 2.6.17-mm3 Martin Bligh
2006-06-27 22:40 ` 2.6.17-mm3: arm: *_irq_wake compile error Adrian Bunk
2006-06-28 7:09 ` Thomas Gleixner
2006-06-28 7:12 ` Andrew Morton
2006-06-28 7:20 ` Thomas Gleixner
2006-06-28 8:13 ` Ingo Molnar
2006-06-28 8:30 ` [patch] genirq: rename desc->handler to desc->chip, sparc64 fix Ingo Molnar
2006-06-28 8:39 ` David Miller
2006-06-28 8:48 ` Andrew Morton
2006-06-28 8:47 ` Ingo Molnar
2006-06-28 9:24 ` David Miller
2006-06-29 4:58 ` Paul Mackerras
2006-06-29 6:42 ` Ingo Molnar
2006-06-28 12:03 ` 2.6.17-mm3 - mutex warning in usbhid, battery problem, and slab corruption Rafael J. Wysocki
2006-06-28 12:09 ` Andrew Morton
2006-06-28 14:14 ` 2.6.17-mm3 Cedric Le Goater
2006-06-28 16:54 ` [-mm patch] make drivers/scsi/aic7xxx/aic79xx_core.:ahd_set_tags() static Adrian Bunk
2006-06-28 16:54 ` [-mm patch] kernel/rcutorture.c: make code static Adrian Bunk
2006-06-28 17:13 ` Paul E. McKenney
2006-06-28 17:17 ` Adrian Bunk
2006-06-28 17:49 ` Paul E. McKenney
2006-06-28 20:18 ` Paul E. McKenney
2006-06-28 16:55 ` [-mm patch] kernel/lockdep.c: possible cleanups Adrian Bunk
2006-06-29 13:49 ` Ingo Molnar
2006-06-28 16:55 ` [-mm patch] fs/ecryptfs/: " Adrian Bunk
2006-06-28 18:40 ` Michael Halcrow
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=351423538.03814@ustc.edu.cn \
--to=wfg@mail.ustc.edu.cn \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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