From: "Adam J. Richter" <adam@yggdrasil.com>
To: kaos@ocs.com.au, rhw@MemAlpha.CX
Cc: 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: Sun, 1 Jul 2001 19:25:11 -0700 [thread overview]
Message-ID: <200107020225.TAA02230@adam.yggdrasil.com> (raw)
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? In other words,
change all commands of the form
dep_tristate CONFIG_FOO 'Foo on x86/pci machines' $CONFIG_PCI $CONFIG_X86
to
dep_tristate CONFIG_FOO 'Foo on x86/pci machines' "$CONFIG_PCI" "$CONFIG_X86"
Then, we could change dep_{bool,tristate} to only treat "" as "n",
in its dependency parameters without effecting how undefined variables
are treated elsewhere. For example, CONFIG_FOO being undefined would
still cause "make oldconfig" to treat it as "NEW" and ask the user
about it.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
next reply other threads:[~2001-07-02 2:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 2:25 Adam J. Richter [this message]
2001-07-02 2:48 ` [PATCH] Re: 2.4.6p6: dep_{bool,tristate} $CONFIG_ARCH_xxx bugs Keith Owens
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=200107020225.TAA02230@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=kaos@ocs.com.au \
--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