From: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>,
Shawn Guo <shawn.guo@linaro.org>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/4] cpufreq: fixes for v3.12
Date: Thu, 12 Sep 2013 09:18:00 +0100 [thread overview]
Message-ID: <523178B8.8020806@arm.com> (raw)
In-Reply-To: <1795989.18GOYqdUtX@vostro.rjw.lan>
On 11/09/13 23:58, Rafael J. Wysocki wrote:
> On Tuesday, September 10, 2013 06:59:45 PM Sudeep KarkadaNagesha wrote:
>> From: Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com>
>>
>> Hi Shawn, Guennadi,
>>
>> These are the fixes for the issue reported by Guennadi.
>> cpu_dev should point to cpu0 device instead of cpufreq-cpu0 platform
>> devices. The dev_id is also updated while registering the cpu clocks.
>>
>> Can you review these ? Tested-by is much appreciated as I don't
>> have hardware to check the fix.
>
> I have a little problem with this series, because the last patch is based
> on the current Linus' tree rather than on my master branch which is what
> I have ready to push. I don't think it makes sense to rebase it, however,
> because that would introduce a merge conflict for Linus unnecessarily.
>
> To avoid merging stuff back and forth, I'll push this series later in the
> cycle.
>
Thanks Rafael.
Let me know in case if you need me to rebase onto your branch.
Regards,
Sudeep
WARNING: multiple messages have this Message-ID (diff)
From: Sudeep.KarkadaNagesha@arm.com (Sudeep KarkadaNagesha)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] cpufreq: fixes for v3.12
Date: Thu, 12 Sep 2013 09:18:00 +0100 [thread overview]
Message-ID: <523178B8.8020806@arm.com> (raw)
In-Reply-To: <1795989.18GOYqdUtX@vostro.rjw.lan>
On 11/09/13 23:58, Rafael J. Wysocki wrote:
> On Tuesday, September 10, 2013 06:59:45 PM Sudeep KarkadaNagesha wrote:
>> From: Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com>
>>
>> Hi Shawn, Guennadi,
>>
>> These are the fixes for the issue reported by Guennadi.
>> cpu_dev should point to cpu0 device instead of cpufreq-cpu0 platform
>> devices. The dev_id is also updated while registering the cpu clocks.
>>
>> Can you review these ? Tested-by is much appreciated as I don't
>> have hardware to check the fix.
>
> I have a little problem with this series, because the last patch is based
> on the current Linus' tree rather than on my master branch which is what
> I have ready to push. I don't think it makes sense to rebase it, however,
> because that would introduce a merge conflict for Linus unnecessarily.
>
> To avoid merging stuff back and forth, I'll push this series later in the
> cycle.
>
Thanks Rafael.
Let me know in case if you need me to rebase onto your branch.
Regards,
Sudeep
next prev parent reply other threads:[~2013-09-12 8:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 17:59 [PATCH 0/4] cpufreq: fixes for v3.12 Sudeep KarkadaNagesha
2013-09-10 17:59 ` Sudeep KarkadaNagesha
2013-09-10 17:59 ` [PATCH 1/4] cpufreq: cpufreq-cpu0: assign cpu_dev correctly to cpu0 device Sudeep KarkadaNagesha
2013-09-10 17:59 ` Sudeep KarkadaNagesha
2013-09-11 8:15 ` Guennadi Liakhovetski
2013-09-11 8:15 ` Guennadi Liakhovetski
2013-09-11 8:42 ` Viresh Kumar
2013-09-11 8:42 ` Viresh Kumar
2013-09-11 8:55 ` Sudeep KarkadaNagesha
2013-09-11 8:55 ` Sudeep KarkadaNagesha
2013-09-11 9:22 ` Shawn Guo
2013-09-11 9:22 ` Shawn Guo
2013-09-11 12:47 ` Rafael J. Wysocki
2013-09-11 12:47 ` Rafael J. Wysocki
2013-09-11 15:43 ` Guennadi Liakhovetski
2013-09-11 15:43 ` Guennadi Liakhovetski
2013-09-10 17:59 ` [PATCH 2/4] cpufreq: imx6q-cpufreq: " Sudeep KarkadaNagesha
2013-09-10 17:59 ` Sudeep KarkadaNagesha
2013-09-10 17:59 ` [PATCH 3/4] ARM: i.MX: change dev_id to cpu0 while registering cpu clock Sudeep KarkadaNagesha
2013-09-10 17:59 ` Sudeep KarkadaNagesha
2013-09-10 17:59 ` [PATCH 4/4] ARM: shmobile: " Sudeep KarkadaNagesha
2013-09-10 17:59 ` Sudeep KarkadaNagesha
2013-09-11 16:25 ` Guennadi Liakhovetski
2013-09-11 16:25 ` Guennadi Liakhovetski
2013-09-10 20:07 ` [PATCH 0/4] cpufreq: fixes for v3.12 Rafael J. Wysocki
2013-09-10 20:07 ` Rafael J. Wysocki
2013-09-11 2:23 ` Shawn Guo
2013-09-11 2:23 ` Shawn Guo
2013-09-11 22:58 ` Rafael J. Wysocki
2013-09-11 22:58 ` Rafael J. Wysocki
2013-09-12 8:18 ` Sudeep KarkadaNagesha [this message]
2013-09-12 8:18 ` Sudeep KarkadaNagesha
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=523178B8.8020806@arm.com \
--to=sudeep.karkadanagesha@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=shawn.guo@linaro.org \
--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 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.