From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Chen Yufan" <chenyufan@vivo.com>,
"Emilio López" <emilio@elopez.com.ar>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>, "Chen-Yu Tsai" <wens@csie.org>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Samuel Holland" <samuel@sholland.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: opensource.kernel@vivo.com
Subject: Re: [PATCH v1] clk: sunxi: sun9i-mmc: Use dev_err_probe() to simplfy code
Date: Fri, 30 Aug 2024 19:53:38 +0200 [thread overview]
Message-ID: <403cc76f-7ba4-412b-9784-af6a6e14cf4a@kernel.org> (raw)
In-Reply-To: <20240830072747.11032-1-chenyufan@vivo.com>
On 30/08/2024 09:27, Chen Yufan wrote:
> Use dev_err_probe() can make code a bit simpler.
>
> Signed-off-by: Chen Yufan <chenyufan@vivo.com>
> ---
> drivers/clk/sunxi/clk-sun9i-mmc.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/clk/sunxi/clk-sun9i-mmc.c b/drivers/clk/sunxi/clk-sun9i-mmc.c
> index 91074017c04f..e6b62e421936 100644
> --- a/drivers/clk/sunxi/clk-sun9i-mmc.c
> +++ b/drivers/clk/sunxi/clk-sun9i-mmc.c
> @@ -134,10 +134,8 @@ static int sun9i_a80_mmc_config_clk_probe(struct platform_device *pdev)
> }
>
> ret = reset_control_deassert(data->reset);
> - if (ret) {
> - dev_err(&pdev->dev, "Reset deassert err %d\n", ret);
> - return ret;
> - }
> + if (ret)
> + return dev_err_probe(&pdev->dev, ret, "Reset deassert err %d\n");
This is ridiculous.
You change something which cannot defer, while leaving other places
which actually can defer and could benefit.
Stop spamming with such low quality patches.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-08-30 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 7:27 [PATCH v1] clk: sunxi: sun9i-mmc: Use dev_err_probe() to simplfy code Chen Yufan
2024-08-30 17:53 ` Krzysztof Kozlowski [this message]
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=403cc76f-7ba4-412b-9784-af6a6e14cf4a@kernel.org \
--to=krzk@kernel.org \
--cc=chenyufan@vivo.com \
--cc=emilio@elopez.com.ar \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mturquette@baylibre.com \
--cc=opensource.kernel@vivo.com \
--cc=samuel@sholland.org \
--cc=sboyd@kernel.org \
--cc=wens@csie.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