On Mon, Jan 10, 2011 at 11:30:33PM +0000, Russell King - ARM Linux wrote:
On Mon, Jan 10, 2011 at 04:24:17PM -0700, Grant Likely wrote:
quoted
I was actually looking at the implementation of clk_enable() which is
called by the driver and doesn't do any NULL checking. But I suppose
that it then becomes the clock-code's own fault if it returns NULL and
then oopses on a NULL being passed to it. Okay, I'll apply it.
Yes absolutely. The clk API must eat whatever cookies it produces,
even if they contain dead flies rather than currants. ;)
nice analogy. :-)
g.