From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: sunran001@208suo.com, gregkh@linuxfoundation.org
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: serial: add missing clk_put()
Date: Tue, 18 Jul 2023 11:40:01 +0300 [thread overview]
Message-ID: <02cc38f9-d742-9695-eb0f-0a5fca096c3a@linaro.org> (raw)
In-Reply-To: <047273ae4e4c25eb7b81fd69d761161e@208suo.com>
On 18/07/2023 10:55, sunran001@208suo.com wrote:
> This patch fixes the following Coccinelle error:
>
> ./drivers/tty/serial/bcm63xx_uart.c:854:2-8: ERROR: missing clk_put;
> clk_get on line 849 and execution via conditional on line 853
>
> Signed-off-by: Ran Sun <sunran001@208suo.com>
> ---
> drivers/tty/serial/bcm63xx_uart.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/tty/serial/bcm63xx_uart.c
> b/drivers/tty/serial/bcm63xx_uart.c
> index 55e82d0bf92d..7353b683952d 100644
> --- a/drivers/tty/serial/bcm63xx_uart.c
> +++ b/drivers/tty/serial/bcm63xx_uart.c
> @@ -851,6 +851,7 @@ static int bcm_uart_probe(struct platform_device *pdev)
> clk = of_clk_get(pdev->dev.of_node, 0);
>
> if (IS_ERR(clk))
> + clk_put(clk);
No!
First, calling clk_put() on the error pointer is incorrect. This will
throw a warning in __clk_put(), but generally passing an error pointer
to another function can cause different kinds of breakage.
Second, you have added the line, but this also moved the return
statement out of the if condition. This way all bcm_uart_probe() calls
will end up with -ENODEV return value.
Please stop blindly fixing the coccinelle warnings. Take care to read
and understand the code.
> return -ENODEV;
>
> port->iotype = UPIO_MEM;
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-07-18 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230718075401.16668-1-xujianghui@cdjrlc.com>
2023-07-18 7:55 ` sunran001
2023-07-18 8:40 ` Dmitry Baryshkov [this message]
2023-07-18 13:25 ` Greg KH
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=02cc38f9-d742-9695-eb0f-0a5fca096c3a@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sunran001@208suo.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 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®