All of lore.kernel.org
 help / color / mirror / Atom feed
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [CPUFREQ] S3C6410: Support 800MHz operation in cpufreq
Date: Thu, 09 Jun 2011 11:29:00 -0700	[thread overview]
Message-ID: <4DF110EC.8030209@samsung.com> (raw)
In-Reply-To: <20110608140238.GB7204@redhat.com>

On 06/08/11 07:02, Dave Jones wrote:
> On Wed, Jun 08, 2011 at 02:49:15PM +0100, Mark Brown wrote:
>   >  At least some newer S3C6410 silicon supports operation up to 800MHz rather
>   >  than just 667MHz. Unfortunately I don't have access to any of documentation
>   >  of this other than some running systems, add a new cpufreq table entry for
>   >  this based on the behaviour of those systems.
>   >
>   >  Signed-off-by: Mark Brown<broonie@opensource.wolfsonmicro.com>
>   >  ---
>   >
>   >  Kukjin already indicated on several occasions that he was happy with
>   >  this change but it never seems to get applied or an actual ack.
>
> applied, thanks.
>
> 	Dave

Dave, could you please add my ack on this?

Acked-by: Kukjin Kim <kgene.kim@samsung.com>

Mark, sorry for late my ack :)

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: Kukjin Kim <kgene.kim@samsung.com>
To: Dave Jones <davej@redhat.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	cpufreq@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] S3C6410: Support 800MHz operation in cpufreq
Date: Thu, 09 Jun 2011 11:29:00 -0700	[thread overview]
Message-ID: <4DF110EC.8030209@samsung.com> (raw)
In-Reply-To: <20110608140238.GB7204@redhat.com>

On 06/08/11 07:02, Dave Jones wrote:
> On Wed, Jun 08, 2011 at 02:49:15PM +0100, Mark Brown wrote:
>   >  At least some newer S3C6410 silicon supports operation up to 800MHz rather
>   >  than just 667MHz. Unfortunately I don't have access to any of documentation
>   >  of this other than some running systems, add a new cpufreq table entry for
>   >  this based on the behaviour of those systems.
>   >
>   >  Signed-off-by: Mark Brown<broonie@opensource.wolfsonmicro.com>
>   >  ---
>   >
>   >  Kukjin already indicated on several occasions that he was happy with
>   >  this change but it never seems to get applied or an actual ack.
>
> applied, thanks.
>
> 	Dave

Dave, could you please add my ack on this?

Acked-by: Kukjin Kim <kgene.kim@samsung.com>

Mark, sorry for late my ack :)

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-09 18:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 13:49 [PATCH] [CPUFREQ] S3C6410: Support 800MHz operation in cpufreq Mark Brown
2011-06-08 13:49 ` [PATCH] " Mark Brown
2011-06-08 14:02 ` [PATCH] [CPUFREQ] " Dave Jones
2011-06-08 14:02   ` [PATCH] " Dave Jones
2011-06-09 18:29   ` Kukjin Kim [this message]
2011-06-09 18:29     ` 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=4DF110EC.8030209@samsung.com \
    --to=kgene.kim@samsung.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.