mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: kaos@ocs.com.au
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
	rhw@MemAlpha.CX, rmk@arm.linux.org.uk
Subject: Re: [PATCH] Re: 2.4.6p6: dep_{bool,tristate} $CONFIG_ARCH_xxx bugs
Date: Sun, 1 Jul 2001 22:52:04 -0700	[thread overview]
Message-ID: <200107020552.WAA02457@adam.yggdrasil.com> (raw)

>On Sun, 1 Jul 2001 21:46:04 -0700, 
>"Adam J. Richter" <adam@yggdrasil.com> wrote:
>>Can you even write a hypothetical example?

>if [ "$CONFIG_foo" = "n" -a "$CONFIG_bar" = "n" ]; then
>  define_bool "$CONFIG_ALLOW_foo_bar n
>fi
>....
>dep_tristate CONFIG_baz $CONFIG_ALLOW_foo_bar

	In linux-2.4.6-pre8, there are only three configuration variables
that are defined with an indented 'define_bool' statement
(CONFIG_BLK_DEV_IDE{DMA,PCI}, and CONFIG_PCI), and the conditional
code execute by all "if" statements in all of the config.in files
appears to be indented (or at least the first statement in the block
is indented).  None of these three variables has the semantics that
I think you you described above.

	If you want to check, I determined this by the following shell
commands:

% find . -iname config.in | xargs egrep dep_tristate | tr '   ' '\n\n' | egrep '^\$CONFIG_' | sort -u > /tmp/config-dependencies 
% find . -iname config.in | xargs egrep '^[   ].*define_bool' | fgrep -f /tmp/config-dependencies  | awk '{print $(NF-1)}' | sort -u
CONFIG_BLK_DEV_IDEDMA
CONFIG_BLK_DEV_IDEPCI
CONFIG_PCI
% find /usr/src/linux/ -iname config.in | xargs egrep -A 2 ^if | egrep -v -e -- | egrep '^-[^         ]'
%
 

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."

             reply	other threads:[~2001-07-02  5:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-02  5:52 Adam J. Richter [this message]
2001-07-02  6:21 ` Keith Owens
2001-07-02 10:14 ` Alan Cox
  -- 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  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-02  2:25 Adam J. Richter
2001-07-02  2:48 ` Keith Owens
2001-07-02  7:22   ` Riley Williams
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=200107020552.WAA02457@adam.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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

all inboxes | Powered by JetHome®