From: Michael Tretter <m.tretter@pengutronix.de>
To: Colin King <colin.king@canonical.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] soc: xilinx: vcu: remove deadcode on null divider check
Date: Thu, 11 Feb 2021 08:31:56 +0100 [thread overview]
Message-ID: <20210211073156.GB30300@pengutronix.de> (raw)
In-Reply-To: <20210210184938.146124-1-colin.king@canonical.com>
On Wed, 10 Feb 2021 18:49:38 +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> The pointer 'divider' has previously been null checked followed by
> a return, hence the subsequent null check is redundant deadcode
> that can be removed. Clean up the code and remove it.
>
> Fixes: 9c789deea206 ("soc: xilinx: vcu: implement clock provider for output clocks")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/clk/xilinx/xlnx_vcu.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/clk/xilinx/xlnx_vcu.c b/drivers/clk/xilinx/xlnx_vcu.c
> index d66b1315114e..607936d7a413 100644
> --- a/drivers/clk/xilinx/xlnx_vcu.c
> +++ b/drivers/clk/xilinx/xlnx_vcu.c
> @@ -512,9 +512,6 @@ static void xvcu_clk_hw_unregister_leaf(struct clk_hw *hw)
>
> mux = clk_hw_get_parent(divider);
> clk_hw_unregister_mux(mux);
> - if (!divider)
> - return;
> -
> clk_hw_unregister_divider(divider);
Thanks for pointing this out. There is actually a different bug there.
There should have been a check for !mux before unregistering the mux:
mux = clk_hw_get_parent(divider);
clk_hw_unregister_divider(divider);
if (!mux)
return;
clk_hw_unregister_mux(mux);
Michael
> }
>
> --
> 2.30.0
>
>
next prev parent reply other threads:[~2021-02-11 7:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 18:49 Colin King
2021-02-11 3:28 ` Stephen Boyd
2021-02-11 7:39 ` Michael Tretter
2021-02-11 19:05 ` Stephen Boyd
2021-03-18 12:48 ` Colin Ian King
2021-03-18 14:44 ` Michael Tretter
2021-02-11 7:31 ` Michael Tretter [this message]
2021-02-11 9:41 ` Colin Ian King
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=20210211073156.GB30300@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®