[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11617025.s66NV700Er@vostro.rjw.lan>
Date: Wed, 11 Sep 2013 15:28:26 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Guennadi Liakhovetski <g.liakhovetski@....de>
Cc: Viresh Kumar <viresh.kumar@...aro.org>, Greg KH <greg@...ah.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
SH-Linux <linux-sh@...r.kernel.org>,
Magnus Damm <magnus.damm@...il.com>
Subject: Re: "cpufreq: fix serialization issues with freq change notifiers" breaks cpufreq too
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 <g.liakhovetski@....de> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists