[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a0cT_AnN_ypFMXPLs=ym12X0FdZ=PXF1r957=h2MhpRDA@mail.gmail.com>
Date: Thu, 30 Mar 2017 17:39:01 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Eric Miao <eric.y.miao@...il.com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>,
Russell King <linux@...linux.org.uk>,
Haojian Zhuang <haojian.zhuang@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ralf Baechle <ralf@...ux-mips.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v5 1/3] ARM: mmp: let clk_disable() return immediately if
clk is NULL
On Tue, Mar 28, 2017 at 11:17 AM, Masahiro Yamada
<yamada.masahiro@...ionext.com> 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.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@...ionext.com>
> ---
>
Applied to next/fixes-non-critical, thanks
Arnd
Powered by blists - more mailing lists