From: Kukjin Kim <kgene.kim@samsung.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH] ARM: S3C24XX: fix missing common.h in mach-s3c24xx/
Date: Thu, 05 Apr 2012 08:10:17 -0700 [thread overview]
Message-ID: <4F7DB5D9.4080106@samsung.com> (raw)
In-Reply-To: <CAP=VYLp-FwEu2AY9wWY7vygmjtZ30AMD=0h8+VtuNVZF2xtTYw@mail.gmail.com>
On 04/03/12 15:33, Paul Gortmaker wrote:
> Hi,
>
> On Wed, Mar 28, 2012 at 8:14 PM, Kukjin Kim<kgene.kim@samsung.com> wrote:
>> This patch fixes missing mach-s3c24xx/common.h which has been
>> lost when regarding s3c24xx directories merged.
>
> Just checking that the updated version of this patch is headed
> in for 3.4 -- we are still seeing the failure in linux-next builds
> and it would be nice to close out the build regressions in there
> as quickly as possible, since they tend to mask other regressions
> from being seen.
>
Hi Paul,
Yeah right and I updated it in my -next.
Thanks.
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: [PATCH] ARM: S3C24XX: fix missing common.h in mach-s3c24xx/
Date: Thu, 05 Apr 2012 08:10:17 -0700 [thread overview]
Message-ID: <4F7DB5D9.4080106@samsung.com> (raw)
In-Reply-To: <CAP=VYLp-FwEu2AY9wWY7vygmjtZ30AMD=0h8+VtuNVZF2xtTYw@mail.gmail.com>
On 04/03/12 15:33, Paul Gortmaker wrote:
> Hi,
>
> On Wed, Mar 28, 2012 at 8:14 PM, Kukjin Kim<kgene.kim@samsung.com> wrote:
>> This patch fixes missing mach-s3c24xx/common.h which has been
>> lost when regarding s3c24xx directories merged.
>
> Just checking that the updated version of this patch is headed
> in for 3.4 -- we are still seeing the failure in linux-next builds
> and it would be nice to close out the build regressions in there
> as quickly as possible, since they tend to mask other regressions
> from being seen.
>
Hi Paul,
Yeah right and I updated it in my -next.
Thanks.
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-05 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 0:14 [PATCH] ARM: S3C24XX: fix missing common.h in mach-s3c24xx/ Kukjin Kim
2012-03-29 0:14 ` Kukjin Kim
2012-03-29 12:28 ` Sergei Shtylyov
2012-03-29 12:28 ` Sergei Shtylyov
2012-03-30 22:58 ` Kukjin Kim
2012-03-30 22:58 ` Kukjin Kim
2012-04-03 22:33 ` Paul Gortmaker
2012-04-03 22:33 ` Paul Gortmaker
2012-04-05 15:10 ` Kukjin Kim [this message]
2012-04-05 15:10 ` 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=4F7DB5D9.4080106@samsung.com \
--to=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-samsung-soc@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.