From: gregkh@linuxfoundation•org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: sirf: use CONFIG_SIRF rather than CONFIG_PRIMA2 where necessary
Date: Mon, 10 Jun 2013 10:38:51 -0700 [thread overview]
Message-ID: <20130610173851.GA2330@kroah.com> (raw)
In-Reply-To: <201306101736.44652.arnd@arndb.de>
On Mon, Jun 10, 2013 at 05:36:44PM +0200, Arnd Bergmann wrote:
> I got a build error today that made me realize that it is not
> possible to build a kernel for a SiRF platform without enabling
> CONFIG_PRIMA2, since a lot of common code depends on CONFIG_PRIMA2.
>
> This fixes all occurences that appear like common SiRF code.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb•de>
> ---
>
> Barry, can you see if this patch makes sense to you?
>
> Mark, Grant, Mike, Greg, Wolfram: would you like to get a split-out
> patch, or should I apply it in one piece to arm-soc?
Feel free to apply it to your tree:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
next prev parent reply other threads:[~2013-06-10 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 15:36 [PATCH] ARM: sirf: use CONFIG_SIRF rather than CONFIG_PRIMA2 where necessary Arnd Bergmann
2013-06-10 15:44 ` Mark Brown
2013-06-10 16:01 ` Wolfram Sang
2013-06-10 17:38 ` Greg Kroah-Hartman [this message]
2013-06-11 0:44 ` Barry Song
2013-06-16 18:23 ` Mike Turquette
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=20130610173851.GA2330@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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