From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] arm: mvebu: update defconfig with 3.7 changes
Date: Fri, 26 Oct 2012 20:56:21 +0000 [thread overview]
Message-ID: <201210262056.21201.arnd@arndb.de> (raw)
In-Reply-To: <9cb693c5-b977-423d-b3a1-569775405bcd@email.android.com>
On Friday 26 October 2012, Jason wrote:
>
> Arnd Bergmann <arnd@arndb•de> wrote:
>
> >On Wednesday 24 October 2012, Thomas Petazzoni wrote:
> >> On Wed, 24 Oct 2012 10:39:42 +0200, Gregory CLEMENT wrote:
> >> > On 10/23/2012 10:17 AM, Thomas Petazzoni wrote:
> >> > > The split of 370 and XP into two Kconfig options and the
> >multiplatform
> >> > > kernel support has changed a few Kconfig symbols, so let's update
> >the
> >> > > mvebu_defconfig file with the latest changes.
> >> >
> >> > Indeed this patch fixes the mvebu_defconfig which was broken.
> >> > But as now mvebu is part of multi_v7_defconfig, shouldn't we just
> >> > removed mvebu_defconfig ?
> >>
> >> I think for now, SoC family specific defconfig files are still
> >> accepted, so I'd prefer to keep mvebu_defconfig around. Multiplatform
> >> is nice for users, but I prefer to build a mvebu-only kernel when I'm
> >> doing kernel development.
> >
> >I'd certainly like to see that patch get merged. Should I just apply it
> >to the fixes branch?
> >
> > Arnd
>
> Please do. I have a few other fixes for v3.7 to do this w/e, but iirc they aren't fixing build breakage.
>
Ok, thanks for the quick reply. Applied now.
Arnd
prev parent reply other threads:[~2012-10-26 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 8:17 [PATCH] arm: mvebu: update defconfig with 3.7 changes Thomas Petazzoni
2012-10-24 8:39 ` Gregory CLEMENT
2012-10-24 9:18 ` Andrew Lunn
2012-10-24 14:16 ` Thomas Petazzoni
2012-10-26 20:33 ` Arnd Bergmann
2012-10-26 20:49 ` Jason
2012-10-26 20:56 ` Arnd Bergmann [this message]
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=201210262056.21201.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--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