From: Russell King <rmk@arm.linux.org.uk>
To: Keith Owens <kaos@ocs.com.au>
Cc: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.5.25 net/core/Makefile
Date: Mon, 22 Jul 2002 09:07:04 +0100 [thread overview]
Message-ID: <20020722090704.A2052@flint.arm.linux.org.uk> (raw)
In-Reply-To: <25972.1027300121@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Mon, Jul 22, 2002 at 11:08:41AM +1000
On Mon, Jul 22, 2002 at 11:08:41AM +1000, Keith Owens wrote:
> It is required if you ever want autoconfigure to work, that
> distinguishes between "" (undefined) and "n" (explicitly turned off).
> Forward planning.
Wouldn't it be better to fix the existing config tools to output "=n"
instead of "# CONFIG_foo is not set" ? IIRC they do the translation
back and forth internally anyway, so it should be just a matter of
removing some code from the tools.
After all, the earlier we update the config tools, the earlier we can
do something with the makefiles (after a reasonable period for things
like mconfig to catch up...)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-07-22 8:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-06 8:30 [patch] 2.5.25 net/core/Makefile Keith Owens
2002-07-09 0:11 ` Dave Jones
2002-07-09 0:30 ` Keith Owens
2002-07-09 0:36 ` Dave Jones
2002-07-09 2:13 ` Keith Owens
2002-07-09 2:24 ` Arnaldo Carvalho de Melo
2002-07-21 23:56 ` Kai Germaschewski
2002-07-22 1:08 ` Keith Owens
2002-07-22 8:07 ` Russell King [this message]
2002-07-22 8:37 ` Roman Zippel
2002-07-22 8:51 ` Andreas Schwab
2002-07-22 8:55 ` Russell King
2002-07-22 9:23 ` Roman Zippel
2002-07-22 14:29 ` Kai Germaschewski
-- strict thread matches above, loose matches on Subject: below --
2002-07-11 3:53 Thunder from the hill
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=20020722090704.A2052@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=kaos@ocs.com.au \
--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