From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Mark CPU_32v6K as depended on CPU_V7
Date: Tue, 31 Aug 2010 16:48:00 +0200 [thread overview]
Message-ID: <20100831144800.GA25102@pengutronix.de> (raw)
In-Reply-To: <20100831135126.19953.11529.stgit@e102109-lin.cambridge.arm.com>
On Tue, Aug 31, 2010 at 02:52:32PM +0100, Catalin Marinas wrote:
> CPU_32v6K is selected by CPU_V7 but it only depends on CPU_V6.
>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Acked-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
> ---
>
> It would be nice to have this patch before 2.6.36 is released to avoid a
> warning introduced by my kbuild patch to warn on selecting options with
> unmet dependencies.
ack, too.
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-08-31 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 13:52 [PATCH] ARM: Mark CPU_32v6K as depended on CPU_V7 Catalin Marinas
2010-08-31 14:48 ` Uwe Kleine-König [this message]
2010-09-01 9:15 ` Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2010-07-10 9:02 Catalin Marinas
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=20100831144800.GA25102@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).