From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Input: wdt87xx_i2c - switch to use dev_err_probe()
Date: Tue, 20 Jan 2026 23:09:09 +0200 [thread overview]
Message-ID: <aW_u9QUfzE23zoE_@smile.fi.intel.com> (raw)
In-Reply-To: <u5nsup2neifb2k3ujtxtcnwzs76ieqdwjr2o45eu5uhwwo3dhw@cjyxn43etrzm>
On Tue, Jan 20, 2026 at 12:40:25PM -0800, Dmitry Torokhov wrote:
> On Tue, Jan 13, 2026 at 09:22:58AM +0100, Andy Shevchenko wrote:
...
> > + struct device *dev = &client->dev;
>
> You introduced a tempo but used it in only one place. I dropped it.
Yes, to avoid churn on converting unrelated places right now. But it may help
in the future.
...
> > - error = devm_request_threaded_irq(&client->dev, client->irq,
> > - NULL, wdt87xx_ts_interrupt,
> > - IRQF_ONESHOT,
> > - client->name, wdt);
> > - if (error) {
> > - dev_err(&client->dev, "request irq failed: %d\n", error);
> > - return error;
> > - }
> > -
> > - return 0;
> > + return devm_request_threaded_irq(dev, client->irq,
> > + NULL, wdt87xx_ts_interrupt,
> > + IRQF_ONESHOT, client->name, wdt);
>
> My preference is to keep "if (error) return error;" even for the last
> call when there are multiple potential points of failure in the
> function, adjusted.
Okay, no problem.
> Applied the updated patch.
Thanks!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-01-20 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 8:22 [PATCH v2 0/2] Input: wdt87xx_i2c - a couple of cleanups Andy Shevchenko
2026-01-13 8:22 ` [PATCH v2 1/2] Input: wdt87xx_i2c - tidy up ACPI ID table Andy Shevchenko
2026-01-20 20:42 ` Dmitry Torokhov
2026-01-20 21:07 ` Andy Shevchenko
2026-01-13 8:22 ` [PATCH v2 2/2] Input: wdt87xx_i2c - switch to use dev_err_probe() Andy Shevchenko
2026-01-20 20:40 ` Dmitry Torokhov
2026-01-20 21:09 ` Andy Shevchenko [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=aW_u9QUfzE23zoE_@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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