From: Thomas Gleixner <tglx@linutronix.de>
To: Yan Zhen <yanzhen@vivo.com>,
ckeepax@opensource.cirrus.com, rf@opensource.cirrus.com
Cc: linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
linux-kernel@vger.kernel.org, opensorce.kernel@vivo.com,
Yan Zhen <yanzhen@vivo.com>
Subject: Re: [PATCH v3] irqchip: madera: Simplify with dev_err_probe()
Date: Mon, 02 Sep 2024 13:50:33 +0200 [thread overview]
Message-ID: <874j6y6zqu.ffs@tglx> (raw)
In-Reply-To: <20240830084620.396417-1-yanzhen@vivo.com>
On Fri, Aug 30 2024 at 16:46, 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.
Is fine? We don't care about fine. The question is whether it is correct
or not. And if so, then there wants to be an explanation why it is correct.
> Changes in v3:
> -Rewrite the subject as 'irqchip: madera:'.
Which is still wrong. Care to read Documentation/process/ ?
> drivers/irqchip/irq-madera.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/irqchip/irq-madera.c b/drivers/irqchip/irq-madera.c
> index acceb6e7fa95..d5ad4466a140 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");
https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#line-breaks
But that's moot as Krzysztof pointed out that this patch just picks a
random instance of the code for no reason.
Thanks,
tglx
prev parent reply other threads:[~2024-09-02 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 8:46 [PATCH v3] irqchip: madera: Simplify with dev_err_probe() Yan Zhen
2024-08-30 17:56 ` Krzysztof Kozlowski
2024-09-02 11:50 ` Thomas Gleixner [this message]
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=874j6y6zqu.ffs@tglx \
--to=tglx@linutronix.de \
--cc=ckeepax@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=opensorce.kernel@vivo.com \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--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