From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-next@vger.kernel.org, Kukjin Kim <kgene.kim@samsung.com>,
Ben Dooks <ben-linux@fluff.org>
Subject: Re: New ARM build coverage (was: linux-next: triage for April 18, 2012)
Date: Fri, 20 Apr 2012 17:59:52 +0000 [thread overview]
Message-ID: <201204201759.52271.arnd@arndb.de> (raw)
In-Reply-To: <CAP=VYLrNpskLQDAw3Udnq7grddi-uD6TDjQQoZUd+FVg2rXPnA@mail.gmail.com>
On Thursday 19 April 2012, Paul Gortmaker wrote:
> ARM folks,
>
> Just a heads up that Stephen expanded the linux-next ARM coverage
> today to add a whole bunch more builds.
>
> Possibly "new" build fails were detected in these configs:
>
> ARM:mackerel_defconfig,ag5evm_defconfig
> ARM:ezx_defconfig
> ARM:mini2440_defconfig
I think this is needed to fix mini2440_defconfig after the platform
files have been moved around.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
diff --git a/arch/arm/configs/mini2440_defconfig b/arch/arm/configs/mini2440_defconfig
index 42da918..082175c 100644
--- a/arch/arm/configs/mini2440_defconfig
+++ b/arch/arm/configs/mini2440_defconfig
@@ -14,6 +14,8 @@ CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_BLK_DEV_BSG is not set
CONFIG_BLK_DEV_INTEGRITY=y
CONFIG_ARCH_S3C24XX=y
+# CONFIG_CPU_S3C2410 is not set
+CONFIG_CPU_S3C2440=y
CONFIG_S3C_ADC=y
CONFIG_S3C24XX_PWM=y
CONFIG_MACH_MINI2440=y
next prev parent reply other threads:[~2012-04-20 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 2:13 New ARM build coverage (was: linux-next: triage for April 18, 2012) Paul Gortmaker
2012-04-20 17:37 ` Arnd Bergmann
2012-04-24 3:28 ` New ARM build coverage Viresh Kumar
2012-04-20 17:59 ` Arnd Bergmann [this message]
2012-04-24 23:50 ` New ARM build coverage (was: linux-next: triage for April 18, 2012) Kukjin Kim
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=201204201759.52271.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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).