From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 08/10] ARM: no longer make CPU targets visible separately
Date: Fri, 27 Feb 2015 13:55:19 +0100 [thread overview]
Message-ID: <CACRpkdbvECKX9FObB0mPv0yAVAQ4nmEwhaYN_sZKBi8YtRGcAw@mail.gmail.com> (raw)
In-Reply-To: <1424967096-261582-2-git-send-email-arnd@arndb.de>
On Thu, Feb 26, 2015 at 5:11 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> Now that realview and integrator always select the correct CPU
> type themselves based on the core tiles, there is no need to
> still have them user-visible in arch/arm/mm/Kconfig. The
> ARM925T symbol has been selected by the only user for many
> years, so that can be removed along with the realview and
> integrator specific ones.
>
> This also solves randconfig build problems on realview.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2015-02-27 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 16:11 [PATCH 07/10] ARM: integrator: use explicit core module options Arnd Bergmann
2015-02-26 16:11 ` [PATCH 08/10] ARM: no longer make CPU targets visible separately Arnd Bergmann
2015-02-27 12:55 ` Linus Walleij [this message]
2015-02-26 16:11 ` [PATCH 09/10] ARM: realview: make all header files local Arnd Bergmann
2015-02-27 12:53 ` [PATCH 07/10] ARM: integrator: use explicit core module options Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2015-11-25 16:32 [PATCH 00/10] ARM: realview multiplatform Arnd Bergmann
2015-11-25 16:32 ` [PATCH 08/10] ARM: no longer make CPU targets visible separately Arnd Bergmann
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=CACRpkdbvECKX9FObB0mPv0yAVAQ4nmEwhaYN_sZKBi8YtRGcAw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--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).