linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: Liao Chang <liaochang1@huawei.com>
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: Sat, 5 Aug 2023 00:16:44 +0200	[thread overview]
Message-ID: <20230804221644.cqmoin6u22mxvouk@intel.intel> (raw)
In-Reply-To: <20230802095737.3957587-9-liaochang1@huawei.com>

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.

Sorry, I missed it in the previous version, mind resending it?

Andi

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-08-04 22:17 UTC|newest]

Thread overview: 26+ 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-08  8:55   ` Markus Elfring
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 [this message]
2023-08-07  2:13     ` Liao, Chang
2023-08-07  8:17       ` Andi Shyti
2023-08-07 10:44         ` Liao, Chang
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=20230804221644.cqmoin6u22mxvouk@intel.intel \
    --to=andi.shyti@kernel.org \
    --cc=aisheng.dong@nxp.com \
    --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=liaochang1@huawei.com \
    --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;
as well as URLs for NNTP newsgroup(s).