From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753228Ab3HCVwE (ORCPT ); Sat, 3 Aug 2013 17:52:04 -0400 Received: from hydra.sisk.pl ([212.160.235.94]:54251 "EHLO hydra.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752810Ab3HCVwC (ORCPT ); Sat, 3 Aug 2013 17:52:02 -0400 From: "Rafael J. Wysocki" To: Viresh Kumar 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 Message-ID: <3427557.z5AT4sQqPo@vostro.rjw.lan> User-Agent: KMail/4.9.5 (Linux/3.10.0+; KDE/4.9.5; x86_64; ; ) In-Reply-To: References: <1976834.StkbCTGYhN@vostro.rjw.lan> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Saturday, August 03, 2013 06:58:35 PM Viresh Kumar wrote: > On 3 August 2013 17:37, Rafael J. Wysocki 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!