From: Andrew Morton <akpm@digeo.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] (2.5;v3) move LOG_BUF_SIZE to header/config
Date: Wed, 18 Dec 2002 11:06:42 -0800 [thread overview]
Message-ID: <3E00C742.E682A93A@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0212181013470.21858-100000@dragon.pdx.osdl.net>
"Randy.Dunlap" wrote:
>
> Linus,
>
> Patch applies to 2.5.52-bk3.
>
> This makes LOG_BUF_LEN (actually its shift value) a configurable
> parameter. It does this by adding a general/common config file
> that can use processor-related dependencies. This new Kconfig file
> is located in linux/kernel/ and is included at the end of each
> arch/*/Kconfig file.
>
> Modified to address comments from Christoph Hellwig, James Cloos,
> and Andrew Morton, who likes it.
>
The reason I like it is that it adds $TOPDIR/kernel/Kconfig. Several
times I've been confronted with the need to put exactly the same thing
into each and every arch/<arch>/Kconfig. There doesn't seem to be a
single all-architectures "general stuff" place at present.
prev parent reply other threads:[~2002-12-18 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 18:31 Randy.Dunlap
2002-12-18 19:06 ` Andrew Morton [this message]
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=3E00C742.E682A93A@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=torvalds@transmeta.com \
/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
Powered by JetHome