cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>, Dave Jones <davej@redhat.com>,
	cpufreq@vger.kernel.org, Kyungmin Park <kmpark@infradead.org>,
	Ben Dooks <ben-linux@fluff.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/5] CPUFREQ/S3C64xx: Move S3C64xx CPUfreq driver into drivers/cpufreq
Date: Wed, 01 Jun 2011 13:30:32 -0700	[thread overview]
Message-ID: <4DE6A168.6090907@samsung.com> (raw)
In-Reply-To: <20110601200146.GC12949@opensource.wolfsonmicro.com>

On 06/01/11 13:01, Mark Brown wrote:
> On Wed, Jun 01, 2011 at 01:00:38PM -0700, Kukjin Kim wrote:
>
>> As I remember, 800Mhz support on S3C6410 is ok and replied about that.
>> Then isn't there any progress in my side?...I'm outside of my office.
>
> Yes, you replied and said it was OK but it's not appeared in -next yet.

Oops, sorry :(

Maybe I missed.
Ok, will apply in my after checking others.

Then if any updates, let you know.

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

      reply	other threads:[~2011-06-01 20:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110601094313.GA23122@opensource.wolfsonmicro.com>
     [not found] ` <1306921493-30911-1-git-send-email-broonie@opensource.wolfsonmicro.com>
2011-06-01  9:55   ` [PATCH 1/5] CPUFREQ/S3C64xx: Move S3C64xx CPUfreq driver into drivers/cpufreq Kyungmin Park
2011-06-01  9:58     ` Mark Brown
2011-06-01 16:45       ` Dave Jones
2011-06-07  0:59         ` Dave Jones
2011-06-01 20:00       ` Kukjin Kim
2011-06-01 20:01         ` Mark Brown
2011-06-01 20:30           ` Kukjin Kim [this message]

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=4DE6A168.6090907@samsung.com \
    --to=kgene.kim@samsung.com \
    --cc=ben-linux@fluff.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=kmpark@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox