From: Keith Owens <kaos@ocs.com.au>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: rhw@MemAlpha.CX, linux-kernel@vger.kernel.org, rmk@arm.linux.org.uk
Subject: Re: [PATCH] Re: 2.4.6p6: dep_{bool,tristate} $CONFIG_ARCH_xxx bugs
Date: Mon, 02 Jul 2001 12:48:26 +1000 [thread overview]
Message-ID: <22864.994042106@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 01 Jul 2001 19:25:11 MST." <200107020225.TAA02230@adam.yggdrasil.com>
On Sun, 1 Jul 2001 19:25:11 -0700,
"Adam J. Richter" <adam@yggdrasil.com> wrote:
> Does anyone know if there is any code that would break if
>we put quotation marks around the $CONFIG_xxxx references in the
>dep_xxx commands in all of the Config.in files?
That has the same problem that AC was worried about. Variables that
used to be treated as "undefined, don't care" are now treated as
"undefined, assume n and forbid".
As long as there is any ambiguity about how a rule is meant to treat
undefined variables, treating all undefined variables as 'n' is not
safe. Before making a global change like this, first verify that no
rule treats undefined variables as "don't care". Otherwise something
will break.
next prev parent reply other threads:[~2001-07-02 2:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 2:25 [PATCH] Re: 2.4.6p6: dep_{bool,tristate} $CONFIG_ARCH_xxx bugs Adam J. Richter
2001-07-02 2:48 ` Keith Owens [this message]
2001-07-02 7:22 ` Riley Williams
-- strict thread matches above, loose matches on Subject: below --
2001-07-02 9:29 Adam J. Richter
2001-07-02 6:03 Adam J. Richter
2001-07-02 5:52 Adam J. Richter
2001-07-02 6:21 ` Keith Owens
2001-07-02 10:14 ` Alan Cox
2001-07-02 4:46 Adam J. Richter
2001-07-02 4:51 ` Keith Owens
2001-07-02 9:29 ` Andrzej Krzysztofowicz
2001-07-02 3:34 Adam J. Richter
2001-07-01 3:00 2.4.6p6: numerous " Keith Owens
2001-07-01 23:04 ` [PATCH] Re: 2.4.6p6: " Riley Williams
2001-07-02 0:39 ` Keith Owens
2001-07-02 7:16 ` Riley Williams
2001-07-02 7:23 ` Keith Owens
2001-07-02 8:25 ` Riley Williams
2001-07-02 9:41 ` Russell King
2001-07-02 12:40 ` Riley Williams
2001-07-02 15:03 ` Russell King
2001-07-02 16:28 ` Nicolas Pitre
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=22864.994042106@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rhw@MemAlpha.CX \
--cc=rmk@arm.linux.org.uk \
/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