All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Aren Moynihan <aren@peacevolution.org>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Chen-Yu Tsai" <wens@csie.org>,
	"Jernej Skrabec" <jernej.skrabec@gmail.com>,
	"Samuel Holland" <samuel@sholland.org>,
	"Kaustabh Chakraborty" <kauschluss@disroot.org>,
	"Barnabás Czémán" <trabarni@gmail.com>,
	"Julien Stephan" <jstephan@baylibre.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev, "Ondrej Jirman" <megi@xff.cz>,
	"Dragan Simic" <dsimic@manjaro.org>,
	phone-devel@vger.kernel.org
Subject: Re: [PATCH v5 6/8] iio: light: stk3310: use dev_err_probe where possible
Date: Sun, 9 Feb 2025 16:47:44 +0200	[thread overview]
Message-ID: <Z6jAEEU2dqn_FJVp@smile.fi.intel.com> (raw)
In-Reply-To: <20250208211325.992280-8-aren@peacevolution.org>

On Sat, Feb 08, 2025 at 04:13:24PM -0500, Aren Moynihan wrote:
> Using dev_err_probe instead of dev_err and return makes the errors

Use dev_err_probe()
dev_err()

> easier to understand by including the error name, and saves a little
> code.

I believe this patch will make more sense before switching to local 'dev'
variable. Then the previous one will have an additional justification as
the "struct device *dev = ...;" lines in some cases will be added already
by this patch.

...

>  	indio_dev = devm_iio_device_alloc(dev, sizeof(*data));
> -	if (!indio_dev) {
> -		dev_err(&client->dev, "iio allocation failed!\n");
> -		return -ENOMEM;
> -	}
> +	if (!indio_dev)
> +		return dev_err_probe(dev, -ENOMEM, "iio allocation failed!\n");

We don't issue the messages for -ENOMEM.

If it's in the current code, add a new patch to drop this message and return an
error code directly.

...

> +	if (ret < 0)

Perhaps, while at it, drop these ' < 0' parts where they are not hinting about
anything.

> +		return dev_err_probe(dev, ret, "device_register failed\n");

-- 
With Best Regards,
Andy Shevchenko




  reply	other threads:[~2025-02-09 14:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-08 21:13 [PATCH v5 0/8] iio: light: stk3310: support powering off during suspend Aren Moynihan
2025-02-08 21:13 ` [PATCH v5 1/8] dt-bindings: iio: light: stk33xx: add vdd and leda regulators Aren Moynihan
2025-02-08 21:13 ` [PATCH v5 2/8] iio: light: stk3310: handle all remove logic with devm callbacks Aren Moynihan
2025-02-08 21:13 ` [PATCH v5 3/8] iio: light: stk3310: implement vdd and leda supplies Aren Moynihan
2025-02-08 21:13 ` [PATCH v5 4/8] iio: light: stk3310: simplify and inline STK3310_REGFIELD macro Aren Moynihan
2025-02-08 21:13 ` [PATCH v5 5/8] iio: light: stk3310: refactor to always make dev a variable Aren Moynihan
2025-02-08 21:13 ` [PATCH v5 6/8] iio: light: stk3310: use dev_err_probe where possible Aren Moynihan
2025-02-09 14:47   ` Andy Shevchenko [this message]
2025-02-11 19:43     ` Jonathan Cameron
2025-02-12 10:43       ` Andy Shevchenko
2025-02-15 20:16     ` Aren
2025-02-08 21:13 ` [PATCH v5 7/8] iio: light: stk3310: log error if reading the chip id fails Aren Moynihan
2025-02-08 21:13 ` [PATCH v5 8/8] arm64: dts: allwinner: pinephone: add power supplies to stk3311 Aren Moynihan

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=Z6jAEEU2dqn_FJVp@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=aren@peacevolution.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jic23@kernel.org \
    --cc=jstephan@baylibre.com \
    --cc=kauschluss@disroot.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=megi@xff.cz \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=samuel@sholland.org \
    --cc=trabarni@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.