From: Kukjin Kim <kgene.kim@samsung.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
robin.randhawa@arm.com, Ben Dooks <ben-linux@fluff.org>,
linux-pm@vger.kernel.org, patches@linaro.org,
Liviu.Dudau@arm.com, linux-kernel@vger.kernel.org,
cpufreq@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Steve.Bannister@arm.com,
arvind.chauhan@arm.com, linaro-kernel@lists.linaro.org,
charles.garcia-tobin@arm.com
Subject: Re: [PATCH 07/18] cpufreq: s3c24xx: move cpufreq driver to drivers/cpufreq
Date: Fri, 26 Apr 2013 01:48:19 +0900 [thread overview]
Message-ID: <51795E53.5030908@samsung.com> (raw)
In-Reply-To: <2264237.NUtkmvZG3W@vostro.rjw.lan>
On 04/24/13 07:59, Rafael J. Wysocki wrote:
[...]
>> 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.
>
> Well, I suppose I can take the original patch, but then it will conflict with
> your tree during merge. Is that not a problem?
>
I think, some conflicts can be occurred but if so, we can fix it before
merge window.
- Kukjin
next prev parent reply other threads:[~2013-04-25 16:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1365079581.git.viresh.kumar@linaro.org>
2013-04-04 12:54 ` [PATCH 07/18] cpufreq: s3c24xx: move cpufreq driver to drivers/cpufreq 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
2013-04-23 22:59 ` Rafael J. Wysocki
2013-04-25 16:48 ` Kukjin Kim [this message]
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
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=51795E53.5030908@samsung.com \
--to=kgene.kim@samsung.com \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=arvind.chauhan@arm.com \
--cc=ben-linux@fluff.org \
--cc=charles.garcia-tobin@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
--cc=robin.randhawa@arm.com \
--cc=viresh.kumar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox