All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Eric Miao <eric.y.miao@gmail.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Russell King <linux@armlinux.org.uk>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 1/3] ARM: mmp: let clk_disable() return immediately if clk is NULL
Date: Thu, 30 Mar 2017 17:39:01 +0200	[thread overview]
Message-ID: <CAK8P3a0cT_AnN_ypFMXPLs=ym12X0FdZ=PXF1r957=h2MhpRDA@mail.gmail.com> (raw)
In-Reply-To: <1490692624-11931-2-git-send-email-yamada.masahiro@socionext.com>

On Tue, Mar 28, 2017 at 11:17 AM, Masahiro Yamada
<yamada.masahiro@socionext.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@socionext.com>
> ---
>
Applied to next/fixes-non-critical, thanks

     Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/3] ARM: mmp: let clk_disable() return immediately if clk is NULL
Date: Thu, 30 Mar 2017 17:39:01 +0200	[thread overview]
Message-ID: <CAK8P3a0cT_AnN_ypFMXPLs=ym12X0FdZ=PXF1r957=h2MhpRDA@mail.gmail.com> (raw)
In-Reply-To: <1490692624-11931-2-git-send-email-yamada.masahiro@socionext.com>

On Tue, Mar 28, 2017 at 11:17 AM, Masahiro Yamada
<yamada.masahiro@socionext.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@socionext.com>
> ---
>
Applied to next/fixes-non-critical, thanks

     Arnd

  reply	other threads:[~2017-03-30 15:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28  9:17 [PATCH v5 0/3] clk: let clk_disable() return immediately if clk is NULL for last 3 clks Masahiro Yamada
2017-03-28  9:17 ` Masahiro Yamada
2017-03-28  9:17 ` [PATCH v5 1/3] ARM: mmp: let clk_disable() return immediately if clk is NULL Masahiro Yamada
2017-03-28  9:17   ` Masahiro Yamada
2017-03-30 15:39   ` Arnd Bergmann [this message]
2017-03-30 15:39     ` Arnd Bergmann
2017-03-28  9:17 ` [PATCH v5 2/3] ARM: w90x900: " Masahiro Yamada
2017-03-28  9:17   ` Masahiro Yamada
2017-03-30 15:38   ` Arnd Bergmann
2017-03-30 15:38     ` Arnd Bergmann
2017-03-28  9:17 ` [PATCH v5 3/3] blackfin: bf609: " Masahiro Yamada
2017-04-13  3:33   ` Masahiro Yamada

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK8P3a0cT_AnN_ypFMXPLs=ym12X0FdZ=PXF1r957=h2MhpRDA@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=eric.y.miao@gmail.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mturquette@baylibre.com \
    --cc=ralf@linux-mips.org \
    --cc=sboyd@codeaurora.org \
    --cc=yamada.masahiro@socionext.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.