From: Roman Zippel <zippel@linux-m68k.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Adrian Bunk <bunk@fs.tum.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
GCS <gcs@lsc.hu>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
vandrove@vc.cvut.cz
Subject: Re: Linux 2.6.3-rc4
Date: Wed, 18 Feb 2004 01:39:31 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.58.0402180129330.7851@serv> (raw)
In-Reply-To: <Pine.LNX.4.58.0402171503150.2154@home.osdl.org>
Hi,
On Tue, 17 Feb 2004, Linus Torvalds wrote:
> What we actually want to say is something like "select I2C=FB_RADEON",
> which makes the minimal dependency of I2C be the same value as FB_RADEON
> (which is a tristate) rather than FB_RADEON_I2C (boolean).
You can do something similiar:
config FB_RADEON
select I2C_ALGOBIT if FB_RADEON_I2C
but then you need the patch below to avoid a bogus warning about recursive
dependecies.
Note that the select mechanism is very simple, it's applied to the
selected symbol very late, so it can override any previous selection, but
this also means it ignores any dependencies of the selected symbol. I have
plans to modify the select mechanism for 2.7, but this will be more
complex, so I added something rather simple instead (it was already quite
late during 2.5).
bye, Roman
--- l/scripts/kconfig/symbol.c 8 Sep 2003 21:18:48 -0000 1.1.1.2
+++ l/scripts/kconfig/symbol.c 18 Feb 2004 00:31:00 -0000
@@ -706,7 +706,7 @@ struct symbol *sym_check_deps(struct sym
goto out;
for (prop = sym->prop; prop; prop = prop->next) {
- if (prop->type == P_CHOICE)
+ if (prop->type == P_CHOICE || prop->type == P_SELECT)
continue;
sym2 = sym_check_expr_deps(prop->visible.expr);
if (sym2)
next prev parent reply other threads:[~2004-02-18 0:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 3:51 Linus Torvalds
2004-02-17 6:19 ` Felix Seeger
2004-02-17 8:54 ` Martin Diehl
2004-02-17 9:27 ` Martin Diehl
2004-02-17 15:39 ` Bartlomiej Zolnierkiewicz
2004-02-17 16:21 ` Linux 2.6.3-rc4 (compile stats) John Cherry
2004-02-17 18:45 ` Linux 2.6.3-rc4 GCS
2004-02-17 19:09 ` Linus Torvalds
2004-02-17 20:05 ` Adrian Bunk
2004-02-17 20:16 ` Linus Torvalds
2004-02-17 22:59 ` Adrian Bunk
2004-02-17 23:11 ` Linus Torvalds
2004-02-17 23:37 ` Radeon issue on x86 Benjamin Herrenschmidt
2004-02-18 0:17 ` Linus Torvalds
2004-02-18 0:33 ` Benjamin Herrenschmidt
2004-02-18 0:00 ` Linux 2.6.3-rc4 Adrian Bunk
2004-02-18 1:28 ` Roman Zippel
2004-02-18 0:39 ` Roman Zippel [this message]
2004-02-18 1:06 ` Roman Zippel
2004-02-18 2:45 ` Roman Zippel
2004-02-18 2:58 ` Linus Torvalds
2004-02-18 0:15 ` Roman Zippel
2004-02-18 0:21 ` GCS
2004-02-17 18:56 ` Jonathan Brown
2004-02-17 19:06 ` Linus Torvalds
2004-02-18 10:18 ` Andreas Happe
2004-02-18 4:06 ` Stephen Rothwell
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=Pine.LNX.4.58.0402180129330.7851@serv \
--to=zippel@linux-m68k.org \
--cc=benh@kernel.crashing.org \
--cc=bunk@fs.tum.de \
--cc=gcs@lsc.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=vandrove@vc.cvut.cz \
/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®