The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yu Jiaoliang <yujiaoliang@vivo.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: opensource.kernel@vivo.com
Subject: Re: [PATCH v1] bus: qcom: Simplify with dev_err_probe()
Date: Fri, 30 Aug 2024 10:09:31 +0200	[thread overview]
Message-ID: <76fb94fb-abb9-4cb7-a477-9839d1bc6287@kernel.org> (raw)
In-Reply-To: <20240829124118.3256437-1-yujiaoliang@vivo.com>

On 29/08/2024 14:41, Yu Jiaoliang wrote:
> Error handling in probe() can be a bit simpler with dev_err_probe().
> 
> Signed-off-by: Yu Jiaoliang <yujiaoliang@vivo.com>
> ---
>  drivers/bus/qcom-ebi2.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/bus/qcom-ebi2.c b/drivers/bus/qcom-ebi2.c
> index c1fef1b4bd89..dbd6a99bcc99 100644
> --- a/drivers/bus/qcom-ebi2.c
> +++ b/drivers/bus/qcom-ebi2.c
> @@ -308,10 +308,8 @@ static int qcom_ebi2_probe(struct platform_device *pdev)
>  		return PTR_ERR(ebi2xclk);
>  
>  	ret = clk_prepare_enable(ebi2xclk);
> -	if (ret) {
> -		dev_err(dev, "could not enable EBI2X clk (%d)\n", ret);
> -		return ret;
> -	}
> +	if (ret)
> +		return dev_err_probe(dev, ret, "could not enable EBI2X clk\n");
>  
>  	ebi2clk = devm_clk_get(dev, "ebi2");
>  	if (IS_ERR(ebi2clk)) {


This cannot defer, so not much benefits. And again you change only one
place.

That's pointless and churn.

Best regards,
Krzysztof


  parent reply	other threads:[~2024-08-30  8:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 12:41 [PATCH v1] bus: qcom: Simplify with dev_err_probe() Yu Jiaoliang
2024-08-30  7:22 ` Dmitry Baryshkov
2024-08-30  8:09 ` Krzysztof Kozlowski [this message]
2024-08-30  8:21   ` 于佼良

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=76fb94fb-abb9-4cb7-a477-9839d1bc6287@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opensource.kernel@vivo.com \
    --cc=yujiaoliang@vivo.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