On Thu, Jan 10, 2013 at 10:31:46AM +0100, Julia Lawall wrote:
> On Thu, 10 Jan 2013, Paul Mundt wrote:
>
> > On Thu, Jan 03, 2013 at 10:40:20AM +0100, Julia Lawall wrote:
> > > There has been a discussion recently about how the result of get_clk
> > > should be an opaque handle, not a value that c
On Thu, 10 Jan 2013, Paul Mundt wrote:
> On Thu, Jan 03, 2013 at 10:40:20AM +0100, Julia Lawall wrote:
> > There has been a discussion recently about how the result of get_clk
> > should be an opaque handle, not a value that can be dereferenced:
> >
> > https://lkml.org/lkml/2012/12/20/105
> >
>
On Thu, Jan 03, 2013 at 10:40:20AM +0100, Julia Lawall wrote:
> There has been a discussion recently about how the result of get_clk
> should be an opaque handle, not a value that can be dereferenced:
>
> https://lkml.org/lkml/2012/12/20/105
>
> There is such a dereference in arch/sh/kernel/cpufr
There has been a discussion recently about how the result of get_clk
should be an opaque handle, not a value that can be dereferenced:
https://lkml.org/lkml/2012/12/20/105
There is such a dereference in arch/sh/kernel/cpufreq.c, in the function
sh_cpufreq_cpu_init:
freq_table = cpuclk->nr_freqs
4 matches
Mail list logo