From: Viresh Kumar <viresh.kumar@linaro.org>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Robin Randhawa <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: Mon, 20 May 2013 10:59:42 +0530 [thread overview]
Message-ID: <CAKohpon97dbLDF0xU7vhf5V+UVeJv7WdeMuZ1jXLUTey2+gD2A@mail.gmail.com> (raw)
In-Reply-To: <2001452.Fn2HjLbNED@vostro.rjw.lan>
On 14 May 2013 18:30, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Tuesday, May 14, 2013 09:36:42 PM Kukjin Kim wrote:
>> Viresh Kumar wrote:
>> >
>> > On 13 May 2013 16:21, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>> > > That doesn't matter I suppose. I can take it, but please rebase it on
>> > top
>> > > of current linux-next.
>> >
>> > I have already done that (attached). But i wasn't sure what Kukjin wants
>> > as
>> > he may report conflicts again and i will ask the same question for 3.12 :)
>> >
>> Since this missed last time, this would be sent to upstream via samsung tree
>> again. It means the conflicts should be handled by myself.
>>
>> Rafael, if you don't mind, let me take this into Samsung tree for v3.11.
>
> Sure, please go ahead.
Kukjin,
I hope you have already applied this for linux-next?
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 07/18] cpufreq: s3c24xx: move cpufreq driver to drivers/cpufreq
Date: Mon, 20 May 2013 10:59:42 +0530 [thread overview]
Message-ID: <CAKohpon97dbLDF0xU7vhf5V+UVeJv7WdeMuZ1jXLUTey2+gD2A@mail.gmail.com> (raw)
In-Reply-To: <2001452.Fn2HjLbNED@vostro.rjw.lan>
On 14 May 2013 18:30, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Tuesday, May 14, 2013 09:36:42 PM Kukjin Kim wrote:
>> Viresh Kumar wrote:
>> >
>> > On 13 May 2013 16:21, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>> > > That doesn't matter I suppose. I can take it, but please rebase it on
>> > top
>> > > of current linux-next.
>> >
>> > I have already done that (attached). But i wasn't sure what Kukjin wants
>> > as
>> > he may report conflicts again and i will ask the same question for 3.12 :)
>> >
>> Since this missed last time, this would be sent to upstream via samsung tree
>> again. It means the conflicts should be handled by myself.
>>
>> Rafael, if you don't mind, let me take this into Samsung tree for v3.11.
>
> Sure, please go ahead.
Kukjin,
I hope you have already applied this for linux-next?
next prev parent reply other threads:[~2013-05-20 5:29 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 12:54 [PATCH 00/18] For-3.10: CPUFreq: Move drivers to drivers/cpufreq Viresh Kumar
2013-04-04 12:54 ` [PATCH 01/18] cpufreq: ARM: Arrange drivers in alphabetical order Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 02/18] cpufreq: tegra: Move driver to drivers/cpufreq Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 03/18] cpufreq: davinci: move cpufreq " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 04/18] cpufreq: pxa3xx: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 05/18] cpufreq: pxa2xx: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 06/18] cpufreq: integrator: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 07/18] cpufreq: s3c24xx: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-05 6:48 ` Kukjin Kim
2013-04-05 6:48 ` Kukjin Kim
2013-04-05 7:06 ` Viresh Kumar
2013-04-05 7:06 ` Viresh Kumar
2013-04-05 11:36 ` Rafael J. Wysocki
2013-04-05 11:36 ` Rafael J. Wysocki
2013-04-05 11:36 ` Rafael J. Wysocki
2013-04-08 9:15 ` Kukjin Kim
2013-04-08 9:15 ` Kukjin Kim
2013-04-08 9:18 ` Viresh Kumar
2013-04-08 9:18 ` Viresh Kumar
2013-04-08 10:46 ` Rafael J. Wysocki
2013-04-08 10:46 ` Rafael J. Wysocki
2013-04-08 10:41 ` Kukjin Kim
2013-04-08 10:41 ` Kukjin Kim
2013-04-23 15:25 ` Kukjin Kim
2013-04-23 15:25 ` Kukjin Kim
2013-04-23 15:25 ` Kukjin Kim
2013-04-23 22:59 ` Rafael J. Wysocki
2013-04-23 22:59 ` Rafael J. Wysocki
2013-04-25 16:48 ` Kukjin Kim
2013-04-25 16:48 ` Kukjin Kim
2013-04-25 18:12 ` Rafael J. Wysocki
2013-04-25 18:12 ` Rafael J. Wysocki
2013-04-25 18:12 ` Rafael J. Wysocki
2013-05-13 6:05 ` Viresh Kumar
2013-05-13 6:05 ` Viresh Kumar
2013-05-13 7:18 ` Why rpm_idle called in rpm_resume ? Feng Hong
2013-05-13 11:55 ` Rafael J. Wysocki
2013-05-13 10:51 ` [PATCH 07/18] cpufreq: s3c24xx: move cpufreq driver to drivers/cpufreq Rafael J. Wysocki
2013-05-13 10:51 ` Rafael J. Wysocki
2013-05-13 10:46 ` Viresh Kumar
2013-05-13 10:46 ` Viresh Kumar
2013-05-14 12:36 ` Kukjin Kim
2013-05-14 12:36 ` Kukjin Kim
2013-05-14 13:00 ` Rafael J. Wysocki
2013-05-14 13:00 ` Rafael J. Wysocki
2013-05-20 5:29 ` Viresh Kumar [this message]
2013-05-20 5:29 ` Viresh Kumar
2013-05-20 13:47 ` Kukjin Kim
2013-05-20 13:47 ` Kukjin Kim
2013-04-08 4:54 ` Viresh Kumar
2013-04-08 4:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 08/18] cpufreq: sa11x0: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 09/18] cpufreq: AVR32: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 10/18] cpufreq: blackfin: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 11/18] cpufreq: cris: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 12/18] cpufreq: ia64: " Viresh Kumar
2013-04-04 12:59 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 13/18] cpufreq: mips: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 14/18] cpufreq: sh: " Viresh Kumar
2013-04-04 12:58 ` Viresh Kumar
2013-04-09 12:55 ` Simon Horman
2013-04-09 12:55 ` Simon Horman
2013-04-09 14:12 ` Viresh Kumar
2013-04-09 14:24 ` Viresh Kumar
2013-04-10 2:12 ` Simon Horman
2013-04-10 2:12 ` Simon Horman
2013-04-10 2:51 ` Viresh Kumar
2013-04-10 2:51 ` Viresh Kumar
2013-04-10 4:30 ` Simon Horman
2013-04-10 4:30 ` Simon Horman
2013-04-04 12:54 ` [PATCH 15/18] cpufreq: unicore2: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 16/18] cpufreq: sparc: " Viresh Kumar
2013-04-04 12:58 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 17/18] cpufreq: powerpc: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-05 6:46 ` Viresh Kumar
2013-04-05 6:46 ` Viresh Kumar
2013-04-09 8:35 ` Viresh Kumar
2013-04-09 8:35 ` Viresh Kumar
2013-04-22 6:49 ` Viresh Kumar
2013-04-22 6:49 ` Viresh Kumar
2013-05-13 6:04 ` Viresh Kumar
2013-05-13 6:04 ` Viresh Kumar
2013-05-20 4:40 ` Viresh Kumar
2013-05-20 4:40 ` Viresh Kumar
2013-05-31 10:50 ` Viresh Kumar
2013-05-31 10:50 ` Viresh Kumar
2013-06-07 5:18 ` Viresh Kumar
2013-06-07 5:18 ` Viresh Kumar
2013-06-07 11:58 ` Rafael J. Wysocki
2013-06-07 11:58 ` Rafael J. Wysocki
2013-04-04 12:54 ` [PATCH 18/18] cpufreq: powerpc/platforms/cell: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 13:02 ` Arnd Bergmann
2013-04-04 13:02 ` Arnd Bergmann
2013-04-04 13:50 ` Viresh Kumar
2013-04-04 13:50 ` Viresh Kumar
2013-04-04 14:48 ` Arnd Bergmann
2013-04-04 14:48 ` Arnd Bergmann
2013-04-04 22:36 ` [PATCH 00/18] For-3.10: CPUFreq: Move drivers " Rafael J. Wysocki
2013-04-05 1:17 ` 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=CAKohpon97dbLDF0xU7vhf5V+UVeJv7WdeMuZ1jXLUTey2+gD2A@mail.gmail.com \
--to=viresh.kumar@linaro.org \
--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=kgene.kim@samsung.com \
--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 \
/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.