From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: rmk@arm.linux.org.uk (Russell King)
Cc: kaos@ocs.com.au (Keith Owens),
adam@yggdrasil.com (Adam J. Richter),
linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.6-pre6: numerous dep_{bool,tristate} $CONFIG_ARCH_xxx bugs
Date: Fri, 29 Jun 2001 16:19:46 +0100 (BST) [thread overview]
Message-ID: <E15G03e-0000Ti-00@the-village.bc.nu> (raw)
In-Reply-To: <20010629153036.A10196@flint.arm.linux.org.uk> from "Russell King" at Jun 29, 2001 03:30:36 PM
> > mainline configs will be much more readable. It also guarantees that
> > any future tests on $CONFIG_ARCH_somearch will work, even if the code
> > does not use if statements.
>
> I'd rather that we fixed dep_* so that undefined symbols were treated as
> 'n', just like the makefiles treat undefined symbols.
That isnt a simple change. dep_tristate is used both to express 'need this'
and also 'conflicts with'. Those are ambiguous. You'd need to extend the
syntax say by adding ${FOO:N} syntax
next prev parent reply other threads:[~2001-06-29 15:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 14:10 Adam J. Richter
2001-06-29 14:21 ` Keith Owens
2001-06-29 14:30 ` Russell King
2001-06-29 14:41 ` Keith Owens
2001-06-29 15:19 ` Alan Cox [this message]
2001-06-29 14:30 ` Jeff Garzik
2001-06-30 4:35 Adam J. Richter
2001-06-30 7:26 ` Alan Cox
2001-06-30 9:20 ` Russell King
2001-06-30 11:43 ` Alan Cox
2001-06-30 11:58 ` Russell King
2001-06-30 12:01 ` Alan Cox
2001-06-30 12:02 ` Russell King
2001-06-30 11:45 ` Keith Owens
2001-06-30 12:10 ` Russell King
2001-06-30 4:40 Adam J. Richter
2001-06-30 7:23 ` Alan Cox
2001-06-30 9:38 Adam J. Richter
2001-06-30 13:32 Adam J. Richter
2001-06-30 14:57 Adam J. Richter
2001-06-30 15:01 ` Russell King
2001-07-01 2:39 ` Keith Owens
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=E15G03e-0000Ti-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=adam@yggdrasil.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--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®