From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linaro-kernel@lists.linaro.org, patches@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, srivatsa.bhat@linux.vnet.ibm.com,
l.majewski@samsung.com
Subject: Re: [PATCH 00/10] CPUFreq: Fixes & Cleanups for 3.12
Date: Sun, 04 Aug 2013 00:02:16 +0200 [thread overview]
Message-ID: <3427557.z5AT4sQqPo@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpok_ZYB3J0QUJMPxBbmRZ9RssYOTYm0KSwAqyH53ydZcRg@mail.gmail.com>
On Saturday, August 03, 2013 06:58:35 PM Viresh Kumar wrote:
> On 3 August 2013 17:37, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Saturday, August 03, 2013 05:19:18 PM Viresh Kumar wrote:
> >> Hi Rafael,
> >>
> >> This patchset tries to fix & cleanup many existing cpufreq core issues. First
> >> four patches tries to cleanup basic problems in cpufreq core. Its first patch
> >> was earlier sent separately but now is part of this series.
> >>
> >> Fifth patch was also sent earlier as reply to your patches and was reviewed by
> >> Srivatsa. Sixth patch was picked from Lukasz's patchset on introducing software
> >> "boost" feature in core. It will be used by this patchset.
> >>
> >> And last four are the most significant part of this set. They try to make many
> >> things simple and robust.
> >>
> >> This is rebased of your bleeding-edge branch + two patches from you:
> >> 18a6b03 cpufreq: Avoid double kobject_put() for the same kobject in error code path
> >> d0cde63 cpufreq: Do not hold driver module references for additional policy CPUs
> >> abe513f Merge branch 'acpi-sleep-next' into linux-next
> >>
> >> They are also pushed in my cpufreq-next branch
> >
> > How much testing has that received so far?
>
> I planned to add this information but forgot at the last moment. It
> was partially
> tested. As it was mostly developed over the weekend I wasn't able to do much
> of testing. I posted it to get early comments, and testing would complete by
> beginning of next week.
OK, thanks!
prev parent reply other threads:[~2013-08-03 21:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 11:49 Viresh Kumar
2013-08-03 11:49 ` [PATCH 01/10] cpufreq: Cleanup header files included in core Viresh Kumar
2013-08-03 17:15 ` Viresh Kumar
2013-08-03 21:42 ` Rafael J. Wysocki
2013-08-03 11:49 ` [PATCH 02/10] cpufreq: Re-arrange declarations in cpufreq.h Viresh Kumar
2013-08-03 17:13 ` Viresh Kumar
2013-08-03 21:43 ` Rafael J. Wysocki
2013-08-03 11:49 ` [PATCH 03/10] cpufreq: Give consistent names for struct cpufreq_policy * Viresh Kumar
2013-08-06 13:38 ` Viresh Kumar
2013-08-06 14:02 ` Rafael J. Wysocki
2013-08-03 11:49 ` [PATCH 04/10] cpufreq: Use sizeof(*ptr) form for finding size of a struct Viresh Kumar
2013-08-03 11:49 ` [PATCH 05/10] cpufreq: Pass policy to cpufreq_add_policy_cpu() Viresh Kumar
2013-08-03 11:49 ` [PATCH 06/10] cpufreq: Store cpufreq policies in a list Viresh Kumar
2013-08-03 11:49 ` [PATCH 07/10] cpufreq: Use cpufreq_policy_list for iterating over policies Viresh Kumar
2013-08-03 11:49 ` [PATCH 08/10] cpufreq: Fix broken usage of governor->owner's refcount Viresh Kumar
2013-08-03 12:08 ` Rafael J. Wysocki
2013-08-03 13:27 ` Viresh Kumar
2013-08-03 22:06 ` Rafael J. Wysocki
2013-08-03 11:49 ` [PATCH 09/10] cpufreq: Don't use cpufreq_driver->owner's refcount to protect critical sections Viresh Kumar
2013-08-03 11:49 ` [PATCH 10/10] cpufreq: Remove struct cpufreq_driver's owner field Viresh Kumar
2013-08-03 12:07 ` [PATCH 00/10] CPUFreq: Fixes & Cleanups for 3.12 Rafael J. Wysocki
2013-08-03 13:28 ` Viresh Kumar
2013-08-03 22:02 ` Rafael J. Wysocki [this message]
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=3427557.z5AT4sQqPo@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=l.majewski@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=srivatsa.bhat@linux.vnet.ibm.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
all inboxes | Powered by JetHome®