Re: [PATCH v4] m68k: let clk_disable() return immediately if clk is NULL

Hi Masahiro, On 19/09/16 04:01, Masahiro Yamada wrote: > In many of clk_disable() implementations, it is a no-op for a NULL > pointer input, but this is one of the exceptions. > > Making it treewide consistent will allow clock consumers to call > clk_disable() without NULL pointer check. > >

Re: [PATCH v4] m68k: let clk_disable() return immediately if clk is NULL

Hi Masahiro, On 19/09/16 04:01, Masahiro Yamada wrote: > In many of clk_disable() implementations, it is a no-op for a NULL > pointer input, but this is one of the exceptions. > > Making it treewide consistent will allow clock consumers to call > clk_disable() without NULL pointer check. > >

[PATCH v4] m68k: let clk_disable() return immediately if clk is NULL

In many of clk_disable() implementations, it is a no-op for a NULL pointer input, but this is one of the exceptions. Making it treewide consistent will allow clock consumers to call clk_disable() without NULL pointer check. Signed-off-by: Masahiro Yamada Acked-by:

[PATCH v4] m68k: let clk_disable() return immediately if clk is NULL

In many of clk_disable() implementations, it is a no-op for a NULL pointer input, but this is one of the exceptions. Making it treewide consistent will allow clock consumers to call clk_disable() without NULL pointer check. Signed-off-by: Masahiro Yamada Acked-by: Greg Ungerer --- Changes in