From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Yan Zhen <yanzhen@vivo.com>, <ckeepax@opensource.cirrus.com>,
<tglx@linutronix.de>, <linus.walleij@linaro.org>
Cc: <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:08:55 +0100 [thread overview]
Message-ID: <82d147d8-8b97-48b1-8e2a-9479bff14f3c@opensource.cirrus.com> (raw)
In-Reply-To: <20240828120118.1284420-1-yanzhen@vivo.com>
On 28/08/2024 13:01, 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 +++----
Split into separate patches for irqchip and pinctrl. There's no
dependency between these two changes so they don't need to be
applied in the same patch.
Also use the correct commit subject prefix for the subsystem and
driver that is being patched. Not "cirrus:".
> 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);
dev_err_probe already logs 'ret' so you don't need to log it again in
the message.
> }
> }
>
> 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);
Same here. No need to log 'ret' twice.
> }
> }
>
next prev parent reply other threads:[~2024-08-28 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 12:01 Yan Zhen
2024-08-28 12:08 ` Richard Fitzgerald [this message]
2024-08-28 12:27 ` Charles Keepax
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=82d147d8-8b97-48b1-8e2a-9479bff14f3c@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=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=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
all inboxes | Powered by JetHome®