From: Keith Owens <kaos@ocs.com.au>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.5.25 net/core/Makefile
Date: Mon, 22 Jul 2002 11:08:41 +1000 [thread overview]
Message-ID: <25972.1027300121@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 21 Jul 2002 18:56:24 EST." <Pine.LNX.4.44.0207211853130.16927-100000@chaos.physics.uiowa.edu>
On Sun, 21 Jul 2002 18:56:24 -0500 (CDT),
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de> wrote:
>Makes sense to me. However, the CONFIG_ variables used in the Makefiles
>are never "n", they are "y", "m" or undefined.
>
>In Config.in scripts you have to cater for "n" or "", and I've seen
>various people on l-k carry this behavior into the Makefiles, but there
>it's unnecessary for all I can tell.
It is required if you ever want autoconfigure to work, that
distinguishes between "" (undefined) and "n" (explicitly turned off).
Forward planning.
next prev parent reply other threads:[~2002-07-22 1:05 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 [this message]
2002-07-22 8:07 ` Russell King
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=25972.1027300121@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=kai@tp1.ruhr-uni-bochum.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