From: "Liao, Chang" <liaochang1@huawei.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: <florian.fainelli@broadcom.com>,
<bcm-kernel-feedback-list@broadcom.com>, <rjui@broadcom.com>,
<sbranden@broadcom.com>, <yangyicong@hisilicon.com>,
<aisheng.dong@nxp.com>, <shawnguo@kernel.org>,
<s.hauer@pengutronix.de>, <kernel@pengutronix.de>,
<festevam@gmail.com>, <linux-imx@nxp.com>, <kblaiech@nvidia.com>,
<asmaa@nvidia.com>, <loic.poulain@linaro.org>, <rfoss@kernel.org>,
<ardb@kernel.org>, <gcherian@marvell.com>,
<linux-i2c@vger.kernel.org>,
<linux-rpi-kernel@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH 8/9] i2c: imx-lpi2c: Use dev_err_probe in probe function
Date: Mon, 7 Aug 2023 18:44:23 +0800 [thread overview]
Message-ID: <042c6eb7-cf31-79e1-51c7-c229e2582c0c@huawei.com> (raw)
In-Reply-To: <20230807081725.fmjvdp3gxjs2ijee@intel.intel>
Hi, Andi
在 2023/8/7 16:17, Andi Shyti 写道:
> On Mon, Aug 07, 2023 at 10:13:30AM +0800, Liao, Chang wrote:
>> Hi, Andi
>>
>> 在 2023/8/5 6:16, Andi Shyti 写道:
>>> On Wed, Aug 02, 2023 at 05:57:36PM +0800, Liao Chang wrote:
>>>> Use the dev_err_probe function instead of dev_err in the probe function
>>>> so that the printed messge includes the return value and also handles
>>>> -EPROBE_DEFER nicely.
>>>>
>>>> Signed-off-by: Liao Chang <liaochang1@huawei.com>
>>>> ---
>>>> drivers/i2c/busses/i2c-imx-lpi2c.c | 12 ++++--------
>>>> 1 file changed, 4 insertions(+), 8 deletions(-)
>>>>
>>>> diff --git a/drivers/i2c/busses/i2c-imx-lpi2c.c b/drivers/i2c/busses/i2c-imx-lpi2c.c
>>>> index c3287c887c6f..bfa788b3775b 100644
>>>> --- a/drivers/i2c/busses/i2c-imx-lpi2c.c
>>>> +++ b/drivers/i2c/busses/i2c-imx-lpi2c.c
>>>> @@ -569,10 +569,8 @@ static int lpi2c_imx_probe(struct platform_device *pdev)
>>>> sizeof(lpi2c_imx->adapter.name));
>>>>
>>>> ret = devm_clk_bulk_get_all(&pdev->dev, &lpi2c_imx->clks);
>>>> - if (ret < 0) {
>>>> - dev_err(&pdev->dev, "can't get I2C peripheral clock, ret=%d\n", ret);
>>>> - return ret;
>>>> - }
>>>> + if (ret < 0)
>>>> + return dev_err_probe(&pdev->dev, ret, "can't get I2C peripheral clock\n");
>>>
>>> you cut on this because the line was going over 100 characters? :)
>>>
>>> In theory you shouldn't change the print message when doing such
>>> changes and you can still split it as:
>>>
>>> return dev_err_probe(&pdev->dev, ret,
>>> "can't get I2C peripheral clock, ret=%d\n",
>>> ret);
>>>
>>> and you're even within the 80 characters.
>>
>> Since dev_err_probe always print the second parameter that happens to be the return value,
>> I remove the "ret=%d" from the original message to avoid a redundant error message.
>>
>> So is it better to keep the original message unchanged, even though dev_err_probe also prints
>> the return error value? Or is it better to make this change so that all error messages printed
>> in the probe function include the return value in a consistent style?
>
> yes, you are right! Then please ignore this comment, but...
>
>>> ret = devm_request_irq(&pdev->dev, irq, lpi2c_imx_isr, 0,
>>> pdev->name, lpi2c_imx);
>>> - if (ret) {
>>> - dev_err(&pdev->dev, "can't claim irq %d\n", irq);
>>> - return ret;
>>> - }
>>> + if (ret)
>>> + return dev_err_probe(&pdev->dev, ret, "can't claim irq %d\n", irq);
>
> please make it coherent to this second part, as well, where the
> error number is printed.
Do you mean to convert it to the following?
if (ret)
return dev_err_probe(&pdev->dev, ret, "can't claim irq\n");
I understand that the style of error message printed by dev_err_probe is like
"error [ERRNO]: [customized message]", the [ERRNO] comes from 2nd parameter,
[customized message] comes from 3rd paramter, if the original [customized message]it
also print ERRNO, i intend to remove it in this patch, otherwise, I will just keep it.
In the above code, [customized message] intend to print irq but return value, so it is
better to keep the original message, right?
Thanks.
>
> Thank you,
> Andi
--
BR
Liao, Chang
next prev parent reply other threads:[~2023-08-07 10:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 9:57 [PATCH v2 0/9] Use dev_err_probe in i2c probe function Liao Chang
2023-08-02 9:57 ` [PATCH 1/9] i2c: bcm2835: Use dev_err_probe in " Liao Chang
2023-08-02 9:57 ` [PATCH 2/9] i2c: mlxbf: " Liao Chang
2023-08-04 22:11 ` Andi Shyti
2023-08-02 9:57 ` [PATCH 3/9] i2c: xlp9xx: " Liao Chang
2023-08-02 9:57 ` [PATCH 4/9] i2c: hisi: " Liao Chang
2023-08-02 9:57 ` [PATCH 5/9] i2c: qcom-cci: " Liao Chang
2023-08-02 9:57 ` [PATCH 6/9] i2c: pxa: " Liao Chang
2023-08-02 9:57 ` [PATCH 7/9] i2c: dln2: " Liao Chang
2023-08-02 9:57 ` [PATCH 8/9] i2c: imx-lpi2c: " Liao Chang
2023-08-04 22:16 ` Andi Shyti
2023-08-07 2:13 ` Liao, Chang
2023-08-07 8:17 ` Andi Shyti
2023-08-07 10:44 ` Liao, Chang [this message]
2023-08-07 11:55 ` Andi Shyti
2023-08-08 1:27 ` Liao, Chang
2023-08-02 9:57 ` [PATCH 9/9] i2c: synquacer: " Liao Chang
2023-08-04 22:18 ` Andi Shyti
2023-08-04 22:19 ` [PATCH v2 0/9] Use dev_err_probe in i2c " Andi Shyti
2023-08-07 2:13 ` Liao, Chang
-- strict thread matches above, loose matches on Subject: below --
2023-07-28 1:31 [PATCH " Liao Chang
2023-07-28 1:31 ` [PATCH 8/9] i2c: imx-lpi2c: Use dev_err_probe in " Liao Chang
2023-07-28 5:55 ` Uwe Kleine-König
2023-07-31 2:16 ` Liao, Chang
2023-07-31 7:34 ` Uwe Kleine-König
2023-08-01 1:23 ` Liao, Chang
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=042c6eb7-cf31-79e1-51c7-c229e2582c0c@huawei.com \
--to=liaochang1@huawei.com \
--cc=aisheng.dong@nxp.com \
--cc=andi.shyti@kernel.org \
--cc=ardb@kernel.org \
--cc=asmaa@nvidia.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=festevam@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=gcherian@marvell.com \
--cc=kblaiech@nvidia.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=loic.poulain@linaro.org \
--cc=rfoss@kernel.org \
--cc=rjui@broadcom.com \
--cc=s.hauer@pengutronix.de \
--cc=sbranden@broadcom.com \
--cc=shawnguo@kernel.org \
--cc=yangyicong@hisilicon.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