From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kconfig: Do not select ARCH_VEXPRESS on ARCH_MULTI_V7
Date: Mon, 19 Nov 2012 17:54:40 +0100 [thread overview]
Message-ID: <20121119175440.1096f725@skate> (raw)
In-Reply-To: <1353343497.3303.34.camel@hornet>
On Mon, 19 Nov 2012 16:44:57 +0000, Pawel Moll wrote:
> It's a bug in vexpress-sysreg driver. 3 hours ago I've posted patch
> removing this code...
>
> https://patchwork.kernel.org/patch/1764801/
>
> Apologies about causing the issue in the first place.
But still, the patch that Fabio raises is interesting: why would
ARCH_VEXPRESS be unconditionally enabled when building an ARM
multiplatform kernel for v6/v7 ? I may want to build a kernel with
several platforms, but not necessarily vexpress, no?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-11-19 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 16:38 [PATCH] ARM: Kconfig: Do not select ARCH_VEXPRESS on ARCH_MULTI_V7 Fabio Estevam
2012-11-19 16:44 ` Pawel Moll
2012-11-19 16:54 ` Thomas Petazzoni [this message]
2012-11-19 16:58 ` Pawel Moll
2012-11-19 17:07 ` Thomas Petazzoni
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=20121119175440.1096f725@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 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.