From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tomasz Figa <tomasz.figa@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: Kconfig fails: big select-based circular dependency
Date: Thu, 12 Jun 2014 13:18:06 +0100 [thread overview]
Message-ID: <20140612121806.GY5099@sirena.org.uk> (raw)
In-Reply-To: <CAMuHMdV0F_FhtJwrzJLbxTbQPKs1XzR=Yb0wjMw2TBuXNPObpA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
On Thu, Jun 12, 2014 at 01:57:03PM +0200, Geert Uytterhoeven wrote:
> Should we have a better separation between select and depends, i.e.
> should kconf plainly reject both being used on the same symbol?
> Is it ever valid to have a symbol that's both selected and used with depends on?
Architecture feature Kconfig symbols typically have the pattern that the
architecture selects ARCH_HAS_FOO and then code that needs the feature
depends on ARCH_HAS_FOO.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-12 12:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 9:09 Russell King - ARM Linux
2014-06-12 9:47 ` Russell King - ARM Linux
2014-06-12 10:22 ` Paul Bolle
2014-06-12 10:49 ` Russell King - ARM Linux
2014-06-12 10:31 ` Arnd Bergmann
2014-06-12 11:34 ` Russell King - ARM Linux
2014-06-12 11:57 ` Geert Uytterhoeven
2014-06-12 12:18 ` Mark Brown [this message]
2014-06-12 12:56 ` Paul Bolle
2014-06-12 12:19 ` Arnd Bergmann
2014-06-12 13:03 ` Russell King - ARM Linux
2014-06-12 13:37 ` Arnd Bergmann
2014-06-12 14:17 ` Russell King - ARM Linux
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=20140612121806.GY5099@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tomasz.figa@gmail.com \
/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®