From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, tglx@kernel.org, christophe.jaillet@wanadoo.fr,
mingo@kernel.org, nabijaczleweli@nabijaczleweli.xyz,
kees@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 6/7] iio: ssp_sensors: Use dev_err_probe
Date: Sun, 19 Apr 2026 18:10:11 +0530 [thread overview]
Message-ID: <02321180-DF23-4133-8BF4-8BC2D91A5F98@gmail.com> (raw)
In-Reply-To: <ad9c7JT-ES7f2Nbi@ashevche-desk.local>
On 15 April 2026 3:09:56 pm IST, Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
>On Wed, Apr 15, 2026 at 10:37:48AM +0530, Sanjay Chitroda wrote:
>
>> dev_err_probe() makes error code handling simpler and handle
>> deferred probe nicely (avoid spamming logs).
>
>...
>
>> struct ssp_data *data;
>
>While at it, introduce a temporary variable
>
> struct device *dev = &spi->dev;
>
>and reuse it below. Note, you may add a new patch to reuse it in the lines that
>are not related to this patch but may utilise the local variable as well.
>
>Actually, you can introduce it earlier in the series, exempli gratia when you
>moved probe to use managed resources.
>
Thank you for the input.
I will add a change to use dev, before devm changes in next series.
>> data = ssp_parse_dt(&spi->dev);
>> - if (!data) {
>> - dev_err(&spi->dev, "Failed to find platform data\n");
>> - return -ENODEV;
>> - }
>> + if (!data)
>> + return dev_err_probe(&spi->dev, -ENODEV,
>> + "Failed to find platform data\n");
>
> return dev_err_probe(dev, -ENODEV, "Failed to find platform data\n");
>
>(And you can leave it one line as trailing string literals are fine to be
> longer 80 even in strict mode. You may even double check with checkpatch,
> it won't complain.)
>
>...and so on...
>
Yes, I'm bit obsessed with 72.
I am considering all new changes with possible single line since last week, again thank you for drawing my attention.
>...
>
>> if (data->fw_dl_state == SSP_FW_DL_STATE_NONE) {
>> ret = ssp_initialize_mcu(data);
>> - if (ret < 0) {
>> - dev_err(&spi->dev, "Initialize_mcu failed\n");
>> - return ret;
>> - }
>> - } else {
>> - dev_err(&spi->dev, "Firmware version not supported\n");
>> - return -EPERM;
>> - }
>> + if (ret < 0)
>> + return dev_err_probe(&spi->dev, ret,
>> + "Initialize_mcu failed\n");
>> + } else
>> + return dev_err_probe(&spi->dev, -EPERM,
>> + "Firmware version not supported\n");
>
>I would now negate the conditional and drop redundant 'else'. Also note
>the missing {} in the 'else' branch as per Coding Style.
>
> if (data->fw_dl_state != SSP_FW_DL_STATE_NONE)
> return dev_err_probe(dev, -EPERM, "Firmware version not supported\n");
>
> ret = ssp_initialize_mcu(data);
> if (ret < 0)
> return dev_err_probe(dev, ret, "Initialize_mcu failed\n");
>
Noted, {} to match with if block style.
I will send changes in next series, drop redundant else and simplify the logic.
next prev parent reply other threads:[~2026-04-19 15:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 5:07 [PATCH v6 0/7] iio: ssp_sensors: improve resource cleanup Sanjay Chitroda
2026-04-15 5:07 ` [PATCH v6 1/7] iio: ssp_sensors: cleanup codestyle warning Sanjay Chitroda
2026-04-19 17:28 ` Jonathan Cameron
2026-04-20 4:28 ` Sanjay Chitroda
2026-04-15 5:07 ` [PATCH v6 2/7] iio: ssp_sensors: cleanup codestyle check Sanjay Chitroda
2026-04-15 9:14 ` Andy Shevchenko
2026-04-19 17:33 ` Jonathan Cameron
2026-04-20 4:29 ` Sanjay Chitroda
2026-04-15 5:07 ` [PATCH v6 3/7] iio: ssp_sensors: factor out pending list add/remove helper(s) Sanjay Chitroda
2026-04-15 9:22 ` Andy Shevchenko
2026-04-15 9:25 ` Andy Shevchenko
2026-04-15 5:07 ` [PATCH v6 4/7] iio: ssp_sensors: drop duplicated wdt timer and work cleanup Sanjay Chitroda
2026-04-15 9:29 ` Andy Shevchenko
2026-04-19 12:32 ` Sanjay Chitroda
2026-04-15 5:07 ` [PATCH v6 5/7] iio: ssp_sensors: convert probe and teardown to devm-managed resources Sanjay Chitroda
2026-04-15 9:33 ` Andy Shevchenko
2026-04-19 12:33 ` Sanjay Chitroda
2026-04-19 17:39 ` Jonathan Cameron
2026-04-15 5:07 ` [PATCH v6 6/7] iio: ssp_sensors: Use dev_err_probe Sanjay Chitroda
2026-04-15 9:39 ` Andy Shevchenko
2026-04-19 12:40 ` Sanjay Chitroda [this message]
2026-04-15 5:07 ` [PATCH v6 7/7] iio: ssp_sensors: reuse embedded RX buffer for SPI transfers Sanjay Chitroda
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=02321180-DF23-4133-8BF4-8BC2D91A5F98@gmail.com \
--to=sanjayembeddedse@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=kees@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
--cc=nuno.sa@analog.com \
--cc=tglx@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