public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: kgene.kim@samsung•com (Kukjin Kim)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 07/18] cpufreq: s3c24xx: move cpufreq driver to drivers/cpufreq
Date: Wed, 24 Apr 2013 00:25:59 +0900	[thread overview]
Message-ID: <5176A807.2090005@samsung.com> (raw)
In-Reply-To: <1769336.FkfMpuXqqb@vostro.rjw.lan>

On 04/05/13 20:36, Rafael J. Wysocki wrote:
> On Friday, April 05, 2013 12:36:34 PM Viresh Kumar wrote:
>> On 5 April 2013 12:18, Kukjin Kim<kgene.kim@samsung•com>  wrote:
>>> Basically, this moving looks good to me, but should be re-worked based on
>>> for-next of samsung tree because this touches too many samsung stuff so this
>>> should be sent to upstream via samsung tree.
>>
>> Hmm... Its already applied in Rafael's tree. But it doesn't mean that
>> it can't be
>> moved to your tree if there is a issue.
>
> Well, I'm dropping it.  Please merge via the Samsung tree.
>

Oops, I missed, maybe I have no more chance to send this to upstream for 
upcoming merge window :-(

Rafael, please take this patch with my ack in your tree, sorry for noise.

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

If any problems, please kindly let me know.

Thanks.

- Kukjin

  parent reply	other threads:[~2013-04-23 15:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1365079581.git.viresh.kumar@linaro.org>
2013-04-04 12:54 ` [PATCH 01/18] cpufreq: ARM: Arrange drivers in alphabetical order Viresh Kumar
2013-04-04 12:54 ` [PATCH 02/18] cpufreq: tegra: Move driver to drivers/cpufreq Viresh Kumar
2013-04-04 12:54 ` [PATCH 03/18] cpufreq: davinci: move cpufreq " Viresh Kumar
2013-04-04 12:54 ` [PATCH 04/18] cpufreq: pxa3xx: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 05/18] cpufreq: pxa2xx: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 06/18] cpufreq: integrator: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 07/18] cpufreq: s3c24xx: " Viresh Kumar
2013-04-05  6:48   ` Kukjin Kim
2013-04-05  7:06     ` Viresh Kumar
2013-04-05 11:36       ` Rafael J. Wysocki
2013-04-08  9:15         ` Kukjin Kim
2013-04-08  9:18           ` Viresh Kumar
2013-04-08 10:46           ` Rafael J. Wysocki
2013-04-08 10:41             ` Kukjin Kim
2013-04-23 15:25         ` Kukjin Kim [this message]
2013-04-23 22:59           ` Rafael J. Wysocki
2013-04-25 16:48             ` Kukjin Kim
2013-04-25 18:12               ` Rafael J. Wysocki
2013-05-13  6:05           ` Viresh Kumar
2013-05-13 10:51             ` Rafael J. Wysocki
2013-05-13 10:46               ` Viresh Kumar
2013-05-14 12:36                 ` Kukjin Kim
2013-05-14 13:00                   ` Rafael J. Wysocki
2013-05-20  5:29                     ` Viresh Kumar
2013-05-20 13:47                       ` Kukjin Kim
2013-04-08  4:54       ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 08/18] cpufreq: sa11x0: " Viresh Kumar

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=5176A807.2090005@samsung.com \
    --to=kgene.kim@samsung$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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