From: Adrian Bunk <bunk@fs.tum.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andrew Morton <akpm@digeo.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [2.5 patch] correct help text for LOG_BUF_SHIFT
Date: Thu, 9 Jan 2003 13:11:32 +0100 [thread overview]
Message-ID: <20030109121132.GP6626@fs.tum.de> (raw)
In-Reply-To: <Pine.GSO.4.21.0301091202511.25052-100000@vervain.sonytel.be>
On Thu, Jan 09, 2003 at 12:04:46PM +0100, Geert Uytterhoeven wrote:
> On Wed, 8 Jan 2003, Linus Torvalds wrote:
> > Andrew Morton <akpm@digeo.com>:
> > o move LOG_BUF_SIZE to header/config
>
> I find the config a bit confusing:
>
> | Kernel log buffer size (128 KB, 64 KB, 32 KB, 16 KB, 8 KB, 4 KB) [16 KB] (NEW) ?
> | Select kernel log buffer size from this list (power of 2).
> | Defaults: 17 (=> 128 KB for S/390)
> | 16 (=> 64 KB for x86 NUMAQ or IA-64)
> | 15 (=> 32 KB for SMP)
> | 14 (=> 16 KB for uniprocessor)
> |
> | Kernel log buffer size (128 KB, 64 KB, 32 KB, 16 KB, 8 KB, 4 KB) [16 KB] (NEW)
>
> E.g. should I enter `14' or `16 KB' (or `16') for `16 KB'?
After reading init/Kconfig it seems the following was intended:
--- linux-2.5.55/init/Kconfig.old 2003-01-09 13:06:43.000000000 +0100
+++ linux-2.5.55/init/Kconfig 2003-01-09 13:08:44.000000000 +0100
@@ -89,11 +89,11 @@
default LOG_BUF_SHIFT_15 if SMP
default LOG_BUF_SHIFT_14
help
- Select kernel log buffer size from this list (power of 2).
- Defaults: 17 (=> 128 KB for S/390)
- 16 (=> 64 KB for x86 NUMAQ or IA-64)
- 15 (=> 32 KB for SMP)
- 14 (=> 16 KB for uniprocessor)
+ Select kernel log buffer size from this list.
+ Defaults: 128 KB for S/390
+ 64 KB for x86 NUMAQ or IA-64
+ 32 KB for SMP
+ 16 KB for uniprocessor
config LOG_BUF_SHIFT_17
bool "128 KB"
> Gr{oetje,eeting}s,
>
> Geert
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-01-09 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 4:35 Linux v2.5.55 Linus Torvalds
2003-01-09 7:24 ` Chris Wedgwood
2003-01-09 11:04 ` Geert Uytterhoeven
2003-01-09 12:11 ` Adrian Bunk [this message]
2003-01-09 16:20 ` [2.5 patch] correct help text for LOG_BUF_SHIFT Randy.Dunlap
2003-01-09 19:17 ` [BK PATCH] USB changes for 2.5.55 Greg KH
2003-01-09 20:21 ` Linus Torvalds
2003-01-09 20:34 ` Greg KH
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=20030109121132.GP6626@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@digeo.com \
--cc=geert@linux-m68k.org \
--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