All of lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] CPUFREQ/S3C64xx: Move S3C64xx CPUfreq driver into drivers/cpufreq
Date: Wed, 1 Jun 2011 21:01:46 +0100	[thread overview]
Message-ID: <20110601200146.GC12949@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4DE69A66.9090002@samsung.com>

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.

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: Kyungmin Park <kmpark@infradead.org>,
	linux-arm-kernel@lists.infradead.org,
	Dave Jones <davej@redhat.com>, Ben Dooks <ben-linux@fluff.org>,
	cpufreq@vger.kernel.org
Subject: Re: [PATCH 1/5] CPUFREQ/S3C64xx: Move S3C64xx CPUfreq driver into drivers/cpufreq
Date: Wed, 1 Jun 2011 21:01:46 +0100	[thread overview]
Message-ID: <20110601200146.GC12949@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4DE69A66.9090002@samsung.com>

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.

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

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01  9:43 [PATCH 0/5] S3C64xx updates Mark Brown
2011-06-01  9:44 ` [PATCH 1/5] CPUFREQ/S3C64xx: Move S3C64xx CPUfreq driver into drivers/cpufreq Mark Brown
2011-06-01  9:44   ` [PATCH 2/5] ARM: SAMSUNG: Add support for pre-sleep/post-restore gpio control Mark Brown
2011-06-01  9:44   ` [PATCH 3/5] ARM: S3C64XX: Ensure VIC based IRQs can be resumed from Mark Brown
2011-06-01  9:44   ` [PATCH 4/5] ARM: S3C6410: Support 800MHz operation in cpufreq Mark Brown
2011-06-01 10:30     ` Sangbeom Kim
2011-06-01 10:40       ` Mark Brown
2011-06-02  0:11         ` Sangbeom Kim
2011-06-02  8:28           ` Mark Brown
2011-06-02  9:41             ` Sangbeom Kim
2011-06-02  9:44               ` Kyungmin Park
2011-06-02  9:50                 ` Jassi Brar
2011-06-02  9:55                   ` Vasily Khoruzhick
2011-06-02  9:56                   ` Mark Brown
2011-06-02  9:57                   ` Kyungmin Park
2011-06-01  9:44   ` [PATCH 5/5] ARM: S3C6410: Add some lower frequencies for 800MHz base clock operation Mark Brown
2011-06-01  9:55   ` [PATCH 1/5] CPUFREQ/S3C64xx: Move S3C64xx CPUfreq driver into drivers/cpufreq Kyungmin Park
2011-06-01  9:55     ` Kyungmin Park
2011-06-01  9:58     ` Mark Brown
2011-06-01  9:58       ` Mark Brown
2011-06-01 16:45       ` Dave Jones
2011-06-01 16:45         ` Dave Jones
2011-06-07  0:59         ` Dave Jones
2011-06-07  0:59           ` Dave Jones
2011-06-01 20:00       ` Kukjin Kim
2011-06-01 20:00         ` Kukjin Kim
2011-06-01 20:01         ` Mark Brown [this message]
2011-06-01 20:01           ` Mark Brown
2011-06-01 20:30           ` Kukjin Kim
2011-06-01 20:30             ` 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=20110601200146.GC12949@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --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 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.