From: Tony Lindgren <tony@atomide.com>
To: Andreas Ruprecht <rupran@einserver.de>
Cc: Russell King <linux@arm.linux.org.uk>, linux-omap@vger.kernel.org
Subject: Re: [BUG(?)] Kconfig warning when selecting ARCH_OMAP1
Date: Mon, 8 Sep 2014 08:35:53 -0700 [thread overview]
Message-ID: <20140908153552.GD3238@atomide.com> (raw)
In-Reply-To: <CA+B2V-+GLEiRcJqVA4=2GX5iY1cWjDd4vWdumD_9ALpxuspg9Q@mail.gmail.com>
* Andreas Ruprecht <rupran@einserver.de> [140907 11:39]:
> Hi all,
>
> I found the following inconsistency in the Kconfig dependencies for
> ARCH_OMAP1 during my research, and as I don't know the exact requirements
> for the OMAP configuration (and how the dependencies could be restructured
> to get rid of the warning), I figured you might be able to help me out.
>
> When selecting ARCH_OMAP1 as the system type, Kconfig issues a warning:
> "warning: (ARCH_OMAP1) selects ARCH_OMAP which has unmet direct
> dependencies (ARCH_MULTI_V6 || ARCH_MULTI_V7)"
>
> When I investigated this further, I found the reason to be as follows:
> - ARCH_OMAP1 selects ARCH_OMAP
> - ARCH_OMAP depends on ARCH_MULTI_V6 || ARCH_MULTI_V7
> - ARCH_MULTI_V{6,7} depend on ARCH_MULTIPLATFORM
> - ARCH_MULTIPLATFORM is in the same choice (System Type -> ARM system type)
> as ARCH_OMAP1, and thus the two can never be enabled at the same time.
>
> Might there be an easy way to resolve this inconsistency by restructuring
> the Kconfig dependencies?
Probably to move the config ARCH_OMAP to plat-omap/Kconfig. Suggested fix
being discussed in the "[PATCH] ARM: omap: fix Kconfig warning" thread FYI.
Regards,
Tony
next parent reply other threads:[~2014-09-08 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+B2V-+GLEiRcJqVA4=2GX5iY1cWjDd4vWdumD_9ALpxuspg9Q@mail.gmail.com>
2014-09-08 15:35 ` Tony Lindgren [this message]
2014-09-07 18:42 [BUG(?)] Kconfig warning when selecting ARCH_OMAP1 Andreas Ruprecht
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=20140908153552.GD3238@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rupran@einserver.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.