From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Yan Zhen <yanzhen@vivo.com>
Cc: <rf@opensource.cirrus.com>, <tglx@linutronix.de>,
<linus.walleij@linaro.org>, <linux-sound@vger.kernel.org>,
<patches@opensource.cirrus.com>, <linux-kernel@vger.kernel.org>,
<linux-gpio@vger.kernel.org>, <opensource.kernel@vivo.com>
Subject: Re: [PATCH v1] cirrus: Simplify with dev_err_probe()
Date: Wed, 28 Aug 2024 13:27:03 +0100 [thread overview]
Message-ID: <Zs8XlyXw421hHjM/@opensource.cirrus.com> (raw)
In-Reply-To: <20240828120118.1284420-1-yanzhen@vivo.com>
On Wed, Aug 28, 2024 at 08:01:18PM +0800, Yan Zhen wrote:
> Switch to use dev_err_probe() to simplify the error path and
> unify a message template.
>
> Using this helper is totally fine even if err is known to never
> be -EPROBE_DEFER.
>
> The benefit compared to a normal dev_err() is the standardized format
> of the error code, it being emitted symbolically and the fact that
> the error code is returned which allows more compact error paths.
>
> Signed-off-by: Yan Zhen <yanzhen@vivo.com>
> ---
> drivers/irqchip/irq-madera.c | 5 ++---
> drivers/pinctrl/cirrus/pinctrl-madera-core.c | 7 +++----
> 2 files changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/irqchip/irq-madera.c b/drivers/irqchip/irq-madera.c
> index acceb6e7fa95..68ebe09baaf6 100644
> --- a/drivers/irqchip/irq-madera.c
> +++ b/drivers/irqchip/irq-madera.c
> @@ -199,9 +199,8 @@ static int madera_irq_probe(struct platform_device *pdev)
> ret = regmap_update_bits(madera->regmap, MADERA_IRQ1_CTRL,
> MADERA_IRQ_POL_MASK, 0);
> if (ret) {
> - dev_err(&pdev->dev,
> - "Failed to set IRQ polarity: %d\n", ret);
> - return ret;
> + return dev_err_probe(&pdev->dev, ret,
> + "Failed to set IRQ polarity: %d\n", ret);
> }
> }
>
> diff --git a/drivers/pinctrl/cirrus/pinctrl-madera-core.c b/drivers/pinctrl/cirrus/pinctrl-madera-core.c
> index 898b197c3738..532fa8ac9a94 100644
> --- a/drivers/pinctrl/cirrus/pinctrl-madera-core.c
> +++ b/drivers/pinctrl/cirrus/pinctrl-madera-core.c
> @@ -1064,10 +1064,9 @@ static int madera_pin_probe(struct platform_device *pdev)
> ret = pinctrl_register_mappings(pdata->gpio_configs,
> pdata->n_gpio_configs);
> if (ret) {
> - dev_err(priv->dev,
> - "Failed to register pdata mappings (%d)\n",
> - ret);
> - return ret;
> + return dev_err_probe(priv->dev, ret,
> + "Failed to register pdata mappings (%d)\n",
> + ret);
> }
Since we are doing a respin anyway also the brackets on the if
should be dropped on both of these as well.
Thanks,
Charles
next prev parent reply other threads:[~2024-08-28 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 12:01 [PATCH v1] cirrus: Simplify with dev_err_probe() Yan Zhen
2024-08-28 12:08 ` Richard Fitzgerald
2024-08-28 12:27 ` Charles Keepax [this message]
2024-08-28 14:47 ` Thomas Gleixner
2024-08-28 14:59 ` Richard Fitzgerald
2024-08-28 16:11 ` Charles Keepax
2024-08-28 18:12 ` Thomas Gleixner
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=Zs8XlyXw421hHjM/@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=tglx@linutronix.de \
--cc=yanzhen@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;
as well as URLs for NNTP newsgroup(s).