From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Ben Dooks' <ben-linux@fluff.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ARM: S3C64XX: Fix section mismatch from cpufreq init
Date: Tue, 15 Mar 2011 12:05:30 +0000 [thread overview]
Message-ID: <20110315120529.GA10848@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <010e01cbe309$29e73460$7db59d20$%kim@samsung.com>
On Tue, Mar 15, 2011 at 09:04:36PM +0900, Kukjin Kim wrote:
> Oops, I missed 'pull request' before 38 :(
> So will apply this into for-next...
No worries, it's a warning fix rather than something urgent.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: S3C64XX: Fix section mismatch from cpufreq init
Date: Tue, 15 Mar 2011 12:05:30 +0000 [thread overview]
Message-ID: <20110315120529.GA10848@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <010e01cbe309$29e73460$7db59d20$%kim@samsung.com>
On Tue, Mar 15, 2011 at 09:04:36PM +0900, Kukjin Kim wrote:
> Oops, I missed 'pull request' before 38 :(
> So will apply this into for-next...
No worries, it's a warning fix rather than something urgent.
next prev parent reply other threads:[~2011-03-15 12:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 14:58 [PATCH] ARM: S3C64XX: Fix section mismatch from cpufreq init Mark Brown
2011-03-10 14:58 ` Mark Brown
2011-03-11 7:51 ` Kukjin Kim
2011-03-11 7:51 ` Kukjin Kim
2011-03-15 12:04 ` Kukjin Kim
2011-03-15 12:04 ` Kukjin Kim
2011-03-15 12:05 ` Mark Brown [this message]
2011-03-15 12:05 ` Mark Brown
2011-03-16 8:38 ` Uwe Kleine-König
2011-03-16 8:38 ` Uwe Kleine-König
2011-03-16 9:49 ` Mark Brown
2011-03-16 9:49 ` Mark Brown
2011-03-16 10:13 ` Uwe Kleine-König
2011-03-16 10:13 ` Uwe Kleine-König
2011-03-16 10:53 ` Mark Brown
2011-03-16 10:53 ` Mark Brown
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=20110315120529.GA10848@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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.