From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S934744AbdC3Pi2 (ORCPT <rfc822;w@1wt.eu>);
        Thu, 30 Mar 2017 11:38:28 -0400
Received: from mail-oi0-f67.google.com ([209.85.218.67]:36269 "EHLO
        mail-oi0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S933979AbdC3PiZ (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 30 Mar 2017 11:38:25 -0400
MIME-Version: 1.0
In-Reply-To: <1490692624-11931-3-git-send-email-yamada.masahiro@socionext.com>
References: <1490692624-11931-1-git-send-email-yamada.masahiro@socionext.com> <1490692624-11931-3-git-send-email-yamada.masahiro@socionext.com>
From: Arnd Bergmann <arnd@arndb.de>
Date: Thu, 30 Mar 2017 17:38:23 +0200
X-Google-Sender-Auth: gAWH-3wsGdsGG6VSXSpOTluqtFI
Message-ID: <CAK8P3a34huU3UNYX8i+3cVMMpz=31yR+2WzmtyOYBP4rPpmwZQ@mail.gmail.com>
Subject: Re: [PATCH v5 2/3] ARM: w90x900: let clk_disable() return immediately
 if clk is NULL
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
        Stephen Boyd <sboyd@codeaurora.org>,
        Ralf Baechle <ralf@linux-mips.org>,
        Michael Turquette <mturquette@baylibre.com>,
        Wan ZongShun <mcuos.com@gmail.com>,
        Russell King <linux@armlinux.org.uk>,
        Linux ARM <linux-arm-kernel@lists.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        arm-soc <arm@kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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>
> Acked-by: Wan Zongshun <mcuos.com@gmail.com>
> ---

Applied to next/fixes-non-critical in arm-soc, I don't think anybody else
was going to apply it. Thanks!

     Arnd

From mboxrd@z Thu Jan  1 00:00:00 1970
From: arnd@arndb.de (Arnd Bergmann)
Date: Thu, 30 Mar 2017 17:38:23 +0200
Subject: [PATCH v5 2/3] ARM: w90x900: let clk_disable() return immediately
 if clk is NULL
In-Reply-To: <1490692624-11931-3-git-send-email-yamada.masahiro@socionext.com>
References: <1490692624-11931-1-git-send-email-yamada.masahiro@socionext.com>
 <1490692624-11931-3-git-send-email-yamada.masahiro@socionext.com>
Message-ID: <CAK8P3a34huU3UNYX8i+3cVMMpz=31yR+2WzmtyOYBP4rPpmwZQ@mail.gmail.com>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

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>
> Acked-by: Wan Zongshun <mcuos.com@gmail.com>
> ---

Applied to next/fixes-non-critical in arm-soc, I don't think anybody else
was going to apply it. Thanks!

     Arnd