From: Kukjin Kim <kgene.kim@samsung.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
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: Tue, 24 Apr 2012 16:50:58 -0700 [thread overview]
Message-ID: <4F973C62.6070102@samsung.com> (raw)
In-Reply-To: <201204201759.52271.arnd@arndb.de>
Arnd Bergmann wrote:
> 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
I tested and it's ok to me.
Thanks, Will apply.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: New ARM build coverage (was: linux-next: triage for April 18, 2012)
Date: Tue, 24 Apr 2012 16:50:58 -0700 [thread overview]
Message-ID: <4F973C62.6070102@samsung.com> (raw)
In-Reply-To: <201204201759.52271.arnd@arndb.de>
Arnd Bergmann wrote:
> 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
I tested and it's ok to me.
Thanks, Will apply.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2012-04-24 23:51 UTC|newest]
Thread overview: 10+ 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-19 2:13 ` Paul Gortmaker
2012-04-20 17:37 ` Arnd Bergmann
2012-04-20 17:37 ` Arnd Bergmann
2012-04-24 3:28 ` New ARM build coverage Viresh Kumar
2012-04-24 3:28 ` Viresh Kumar
2012-04-20 17:59 ` New ARM build coverage (was: linux-next: triage for April 18, 2012) Arnd Bergmann
2012-04-20 17:59 ` Arnd Bergmann
2012-04-24 23:50 ` Kukjin Kim [this message]
2012-04-24 23:50 ` 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=4F973C62.6070102@samsung.com \
--to=kgene.kim@samsung.com \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.