On Mon, Feb 11, 2013 at 02:40:39PM +0530, Viresh Kumar wrote: > On 11 February 2013 14:22, Fengguang Wu <fengguang.wu@xxxxxxxxx> wrote: > > Greetings, > > Hi Fengguang, > > > I got the below oops and the first bad commit is > > > > commit 50f6802f8dccb7bbad29010e57973d46b7e7a07e > > Author: Viresh Kumar <viresh.kumar@xxxxxxxxxx> > > Date: Thu Feb 7 10:55:00 2013 +0530 > > There is something really wrong. This problem was earlier reported > and was fixed immediately. And shouldn't be there with linux-next > branch of Rafael. > > What tree are you working on ? > > Even in linux-next/master i see above commit as: > > commit 2eaa3e2df185997e92596ab14a2a67dde3876d2e > Author: Viresh Kumar <viresh.kumar@xxxxxxxxxx> > Date: Thu Feb 7 10:55:00 2013 +0530 > > cpufreq: Fix locking issues Viresh, I confirmed that the updated commit is fine. Sorry for the noise! Fengguang -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
