From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: default to multi_v7_defconfig
Date: Thu, 31 Dec 2015 16:11:54 +0100 [thread overview]
Message-ID: <5177946.MPbmr7k9Kd@wuerfel> (raw)
In-Reply-To: <20151222101834.GE32623@arm.com>
On Tuesday 22 December 2015 10:18:35 Will Deacon wrote:
> On Fri, Dec 18, 2015 at 11:44:23PM +0100, Arnd Bergmann wrote:
> > versatile_defconfig has not been a reasonable default for a very long
> > time, there is very little work happening on this platform and it's
> > based on an old ARM926 CPU core.
> >
> > This changes the default to multi_v7_defconfig, which is much more
> > relevant to anyone doing a build test on ARM, as it covers a wide
> > range of platforms.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >
> > diff --git a/arch/arm/Makefile b/arch/arm/Makefile
> > index 2c2b28ee4811..e9fb67913e6e 100644
> > --- a/arch/arm/Makefile
> > +++ b/arch/arm/Makefile
> > @@ -30,9 +30,8 @@ GZFLAGS :=-9
> > # Never generate .eh_frame
> > KBUILD_CFLAGS += $(call cc-option,-fno-dwarf2-cfi-asm)
> >
> > -# Do not use arch/arm/defconfig - it's always outdated.
> > -# Select a platform tht is kept up-to-date
> > -KBUILD_DEFCONFIG := versatile_defconfig
> > +# This should work on most of the modern platforms
> > +KBUILD_DEFCONFIG := multi_v7_defconfig
> >
> > # defines filename extension depending memory management type.
> > ifeq ($(CONFIG_MMU),)
>
> Acked-by: Will Deacon <will.deacon@arm.com>
...
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
I've applied this patch to the next/defconfig branch of arm-soc now,
as it seems to fit in with the defconfig changes better than in Russell's
tree.
Thanks,
Arnd
prev parent reply other threads:[~2015-12-31 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 22:44 [PATCH] ARM: default to multi_v7_defconfig Arnd Bergmann
2015-12-22 10:06 ` Linus Walleij
2015-12-22 10:18 ` Will Deacon
2015-12-31 15:11 ` 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=5177946.MPbmr7k9Kd@wuerfel \
--to=arnd@arndb.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).