Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753993Ab3IKNR0 (ORCPT ); Wed, 11 Sep 2013 09:17:26 -0400 Received: from hydra.sisk.pl ([212.160.235.94]:44913 "EHLO hydra.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753431Ab3IKNRY (ORCPT ); Wed, 11 Sep 2013 09:17:24 -0400 From: "Rafael J. Wysocki" To: Guennadi Liakhovetski Cc: Viresh Kumar , Greg KH , "Rafael J. Wysocki" , Linux Kernel Mailing List , "linux-arm-kernel@lists.infradead.org" , "linux-pm@vger.kernel.org" , "cpufreq@vger.kernel.org" , SH-Linux , Magnus Damm Subject: Re: "cpufreq: fix serialization issues with freq change notifiers" breaks cpufreq too Date: Wed, 11 Sep 2013 15:28:26 +0200 Message-ID: <11617025.s66NV700Er@vostro.rjw.lan> User-Agent: KMail/4.10.5 (Linux/3.11.0+; KDE/4.10.5; x86_64; ; ) In-Reply-To: References: 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 Content-Length: 1169 Lines: 29 On Wednesday, September 11, 2013 10:15:53 AM Guennadi Liakhovetski wrote: > On Wed, 11 Sep 2013, Viresh Kumar wrote: > > > On 10 September 2013 22:37, Guennadi Liakhovetski wrote: > > > On Tue, 10 Sep 2013, Viresh Kumar wrote: > > >> Quite straight forward actually.. > > > > > > Apparently, not quite. > > > > I overlooked the situation where we return early from ->target() routines.. :( > > > > Please try attached patches, I will repost them later (once I am able to > > convince Rafael that these are really important :) ) > > I'd rather wait until Rafael is convinced, then we'll see. I'm going to revert the commit that was the source of these issues, but that doesn't mean that everything is now rosy. We need to fix the concurrency problems that Viresh was trying to fix in that commit, so it would be nice if you could verify whether or not he is on the right track. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/