
viresh.kumar at linaro
Aug 11, 2013, 9:59 PM
Post #2 of 2
(8 views)
Permalink
|
|
Re: [cpufreq] BUG: unable to handle kernel NULL pointer dereference at (null)
[In reply to]
|
|
On Sun, Aug 11, 2013 at 11:23 AM, Fengguang Wu <fengguang.wu [at] intel> wrote: > Greetings, > > I got the below dmesg and the first bad commit is > > commit 01e3e82efc6742d5cf7ba14fb7a9bea318b386d8 > Author: Lukasz Majewski <l.majewski [at] samsung> > Date: Tue Aug 6 22:53:08 2013 +0530 > > cpufreq: Store cpufreq policies in a list > > Policies available in the cpufreq framework are now linked together. > They are accessible via cpufreq_policy_list defined in the cpufreq > core. > > Signed-off-by: Lukasz Majewski <l.majewski [at] samsung> > Signed-off-by: Myungjoo Ham <myungjoo.ham [at] samsung> > Signed-off-by: Viresh Kumar <viresh.kumar [at] linaro> > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki [at] intel> Its already fixed by: c88a1f8b96e7384627b918dfabbfc0c615a4a914 in Rafael's bleeding-edge branch.. Thanks for reporting. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo [at] vger More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|