From: Konrad Dybcio <konradybcio@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
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, Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH v1] soc: qcom: pbs: Simplify with dev_err_probe()
Date: Fri, 30 Aug 2024 12:03:20 +0200 [thread overview]
Message-ID: <10fad15b-d2a6-4ec1-8af7-bde8f7bf39be@kernel.org> (raw)
In-Reply-To: <894145dc-46fb-451f-a461-d0b9ff1e50dd@kernel.org>
On 30.08.2024 10:08 AM, Krzysztof Kozlowski wrote:
> On 29/08/2024 14:48, 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/soc/qcom/qcom-pbs.c | 7 +++----
>> 1 file changed, 3 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/soc/qcom/qcom-pbs.c b/drivers/soc/qcom/qcom-pbs.c
>> index 77a70d3d0d0b..ab9de12ec901 100644
>> --- a/drivers/soc/qcom/qcom-pbs.c
>> +++ b/drivers/soc/qcom/qcom-pbs.c
>> @@ -201,10 +201,9 @@ static int qcom_pbs_probe(struct platform_device *pdev)
>> }
>>
>> ret = device_property_read_u32(pbs->dev, "reg", &val);
>> - if (ret < 0) {
>> - dev_err(pbs->dev, "Couldn't find reg, ret = %d\n", ret);
>> - return ret;
>> - }
>> + if (ret < 0)
>> + return dev_err_probe(pbs->dev, ret, "Couldn't find reg\n");
>
> This cannot defer, so not much benefits. And you ignore other place in
> the probe()... That's like a weird pattern with all your patches change
> something irrelevant, but leave other places unchanged.
>
> That's pointless and churn.
Hm, that's a good point.. Maybe the static checker folks could come up
with a way that would find functions that call something that can defer
at one point or another and suggest (not) using dev_err_probe with W=1/2..
(although that is probably not going to be very high prio given all the
other static checker issues we're still yet to resolve)
Unless we have something like that already? +CC Dan
Konrad
next prev parent reply other threads:[~2024-08-30 10:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 12:48 [PATCH v1] soc: qcom: pbs: Simplify with dev_err_probe() Yu Jiaoliang
2024-08-29 23:48 ` Konrad Dybcio
2024-08-30 8:08 ` Krzysztof Kozlowski
2024-08-30 10:03 ` Konrad Dybcio [this message]
2024-08-30 15:19 ` Dan Carpenter
2024-08-30 15:31 ` Konrad Dybcio
2024-09-04 18:55 ` Dan Carpenter
2024-09-05 12:35 ` Konrad Dybcio
2024-08-30 10:52 ` 于佼良
2024-08-30 10:57 ` Krzysztof Kozlowski
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=10fad15b-d2a6-4ec1-8af7-bde8f7bf39be@kernel.org \
--to=konradybcio@kernel.org \
--cc=andersson@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=krzk@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