From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: Kconfig fails: big select-based circular dependency
Date: Thu, 12 Jun 2014 14:56:30 +0200 [thread overview]
Message-ID: <1402577790.10273.30.camel@x220> (raw)
In-Reply-To: <20140612121806.GY5099@sirena.org.uk>
On Thu, 2014-06-12 at 13:18 +0100, Mark Brown wrote:
> 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.
A similar usage can be seen with Kconfig symbols with a HAVE_BAR name.
Paul Bolle
next prev parent reply other threads:[~2014-06-12 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 9:09 Kconfig fails: big select-based circular dependency 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
2014-06-12 12:56 ` Paul Bolle [this message]
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=1402577790.10273.30.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).