From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: only select ARM_PATCH_PHYS_VIRT if MMU is enabled
Date: Mon, 7 Jul 2014 08:51:41 +0200 [thread overview]
Message-ID: <20140707065141.GC7827@pengutronix.de> (raw)
In-Reply-To: <20140702103512.GG32514@n2100.arm.linux.org.uk>
Hello,
(adding Yann and linux-kbuild to recipents)
On Wed, Jul 02, 2014 at 11:35:12AM +0100, Russell King - ARM Linux wrote:
> On Wed, Jul 02, 2014 at 11:57:23AM +0200, Uwe Kleine-K?nig wrote:
> > This fixes the following warning:
> >
> > warning: (ARCH_MULTIPLATFORM && ARCH_INTEGRATOR && ARCH_SHMOBILE_LEGACY) selects ARM_PATCH_PHYS_VIRT which has unmet direct dependencies (!XIP_KERNEL && MMU && (!ARCH_REALVIEW || !SPARSEMEM))
> >
> > Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
> > ---
> > I'm not sure why ARCH_MULTIPLATFORM appears here. It depends on MMU,
> > isn't selectable at the same time as ARCH_REALVIEW and XIP_KERNEL
> > depends on !ARCH_MULTIPLATFORM.
>
> The message is extremely confusing. It would read better if those
> && were || - because ARM_PATCH_PHYS_VIRT is selected by
> ARCH_MULTIPLATFORM _or_ ARCH_INTEGRATOR _or_ ARCH_SHMOBILE_LEGACY:
right, so there are two things that could be improved here. The
resolution I'd prefer is to make this two warnings:
ARCH_INTEGRATOR selects ARM_PATCH_PHYS_VIRT which has unmet direct dependencies (!XIP_KERNEL && MMU)
ARCH_SHMOBILE_LEGACY selects ARM_PATCH_PHYS_VIRT which has unmet direct dependencies (!XIP_KERNEL && MMU)
ARCH_REALVIEW cannot be selected at the same time as ARCH_INTEGRATOR or
ARCH_SHMOBILE_LEGACY, so that can be dropped. And as stated above
ARCH_MULTIPLATFORM isn't an issue.
This doesn't have the natural language problem that ARCH_MULTIPLATFORM
*and* ARCH_INTEGRATOR *and* ARCH_SHMOBILE_LEGACY all select
ARM_PATCH_PHYS_VIRT.
> config ARCH_MULTIPLATFORM
> select ARM_PATCH_PHYS_VIRT
>
> config ARCH_INTEGRATOR
> select ARM_PATCH_PHYS_VIRT
>
> config ARCH_SHMOBILE_LEGACY
> select ARM_PATCH_PHYS_VIRT
>
(For reference, the patch did:
- select ARM_PATCH_PHYS_VIRT
+ select ARM_PATCH_PHYS_VIRT if MMU
for ARCH_INTEGRATOR and ARCH_SHMOBILE_LEGACY)
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2014-07-07 6:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 9:57 [PATCH 1/3] ARM: exynos: remove unused <mach/memory.h> Uwe Kleine-König
2014-07-02 9:57 ` [PATCH 2/3] ARM: remove remaining definitions of PLAT_PHYS_OFFSET from <mach/memory.h> Uwe Kleine-König
2014-07-02 10:38 ` Russell King - ARM Linux
2014-07-02 16:15 ` Uwe Kleine-König
2014-07-02 16:18 ` Russell King - ARM Linux
2014-07-07 7:13 ` [PATCH v2 " Uwe Kleine-König
2014-07-25 0:06 ` Russell King - ARM Linux
2014-07-25 9:09 ` Uwe Kleine-König
2014-07-25 12:21 ` Uwe Kleine-König
2014-07-02 9:57 ` [PATCH 3/3] ARM: only select ARM_PATCH_PHYS_VIRT if MMU is enabled Uwe Kleine-König
2014-07-02 10:35 ` Russell King - ARM Linux
2014-07-07 6:51 ` Uwe Kleine-König [this message]
2014-07-08 11:47 ` [PATCH 1/3] ARM: exynos: remove unused <mach/memory.h> Tomasz Figa
2014-07-08 15:20 ` Sachin Kamat
2014-07-22 7:51 ` Uwe Kleine-König
2014-07-22 16:14 ` Olof Johansson
2014-07-22 23:37 ` Kukjin Kim
2014-07-23 19:58 ` Uwe Kleine-König
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=20140707065141.GC7827@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).