From: Dave Jones <davej@redhat.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: Tushar Behera <tushar.behera@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] [CPUFREQ] Move compile for S3C64XX cpufreq to /drivers/cpufreq
Date: Mon, 6 Jun 2011 23:26:11 -0400 [thread overview]
Message-ID: <20110607032610.GA26544@redhat.com> (raw)
In-Reply-To: <4DED98A7.1050202@samsung.com>
On Mon, Jun 06, 2011 at 08:19:03PM -0700, Kukjin Kim wrote:
> On 06/06/11 20:16, Tushar Behera wrote:
> > Hi,
> >
>
> (snip)
>
> >> + This adds the CPUFreq driver for Samsung S5C6410 SoC.
> > S3C6410?
>
> Oops, typo.
> Tushar, thanks for your pointing out :)
>
> Dave, if you need to re-submit for above, please let me know.
no problem, I'll fix it up and recreate the tree.
Dave
WARNING: multiple messages have this Message-ID (diff)
From: davej@redhat.com (Dave Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [CPUFREQ] Move compile for S3C64XX cpufreq to /drivers/cpufreq
Date: Mon, 6 Jun 2011 23:26:11 -0400 [thread overview]
Message-ID: <20110607032610.GA26544@redhat.com> (raw)
In-Reply-To: <4DED98A7.1050202@samsung.com>
On Mon, Jun 06, 2011 at 08:19:03PM -0700, Kukjin Kim wrote:
> On 06/06/11 20:16, Tushar Behera wrote:
> > Hi,
> >
>
> (snip)
>
> >> + This adds the CPUFreq driver for Samsung S5C6410 SoC.
> > S3C6410?
>
> Oops, typo.
> Tushar, thanks for your pointing out :)
>
> Dave, if you need to re-submit for above, please let me know.
no problem, I'll fix it up and recreate the tree.
Dave
next prev parent reply other threads:[~2011-06-07 3:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 1:43 [PATCH] [CPUFREQ] Move compile for S3C64XX cpufreq to /drivers/cpufreq Kukjin Kim
2011-06-07 1:43 ` Kukjin Kim
2011-06-07 3:16 ` Tushar Behera
2011-06-07 3:16 ` Tushar Behera
2011-06-07 3:19 ` Kukjin Kim
2011-06-07 3:19 ` Kukjin Kim
2011-06-07 3:26 ` Dave Jones [this message]
2011-06-07 3:26 ` Dave Jones
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=20110607032610.GA26544@redhat.com \
--to=davej@redhat.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tushar.behera@linaro.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 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.