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, sakari.ailus@linux.intel.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/6] iio: accel: mma8452: use local struct device
Date: Thu, 23 Apr 2026 08:06:20 +0530 [thread overview]
Message-ID: <BA5F2EF9-C439-47A2-BE91-4ED6E12F2EBA@gmail.com> (raw)
In-Reply-To: <aekjBaFT8xvM64zh@ashevche-desk.local>
On 23 April 2026 1:05:33 am IST, Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
>On Wed, Apr 22, 2026 at 10:26:40PM +0530, Sanjay Chitroda wrote:
>
>> Introduce a local struct device pointer derived from &client->dev.
>> This avoids repeated &client->dev usage and improves readability.
>
>...
>
>> static int mma8452_set_runtime_pm_state(struct i2c_client *client, bool on)
>> {
>> #ifdef CONFIG_PM
>
>So, this seems to be a missed in the PM patch.
>
>> int ret;
>> + struct device *dev = &client->dev;
>
>Keep it in reversed xmas tree order.
>
Understood, along with headers would attempt to keep all local variables also in chronological order.
>> if (on)
>> - ret = pm_runtime_resume_and_get(&client->dev);
>> + ret = pm_runtime_resume_and_get(dev);
>> else
>> - ret = pm_runtime_put_autosuspend(&client->dev);
>> + ret = pm_runtime_put_autosuspend(dev);
>> if (ret < 0) {
>> - dev_err(&client->dev,
>> + dev_err(dev,
>> "failed to change power state to %d\n", on);
>>
>> return ret;
>
>> }
>
>...
>
>> static int mma8452_probe(struct i2c_client *client)
>> {
>> struct mma8452_data *data;
>> + struct device *dev = &client->dev;
>
>Same here, reversed xmas tree order.
>
>> struct iio_dev *indio_dev;
>> int ret;
>
Sure, understood.
>...
>
>> data->chip_info = i2c_get_match_data(client);
>> if (!data->chip_info)
>> - return dev_err_probe(&client->dev, -ENODEV,
>> + return dev_err_probe(dev, -ENODEV,
>> "unknown device model\n");
>
>Now it's a single line.
>
>...
>
>> ret = regulator_enable(data->vdd_reg);
>> if (ret) {
>> - dev_err(&client->dev, "failed to enable VDD regulator!\n");
>> + dev_err(dev, "failed to enable VDD regulator!\n");
>> return ret;
>
>Convert this to dev_err_probe() before doing this patch. In that patch you
>introduce temporary dev variable already. Here will use in the other places.
>
Agree with you, will rebase in next series.
>> }
>>
>> ret = regulator_enable(data->vddio_reg);
>> if (ret) {
>> - dev_err(&client->dev, "failed to enable VDDIO regulator!\n");
>> + dev_err(dev, "failed to enable VDDIO regulator!\n");
>> goto disable_regulator_vdd;
>
>Ditto.
>
Sure.
>> }
>
>...
>
>> + pm_runtime_set_autosuspend_delay(dev,
>> MMA8452_AUTO_SUSPEND_DELAY_MS);
>
>Now a single line.
>
next prev parent reply other threads:[~2026-04-23 2:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 16:56 [PATCH v2 0/6] iio: accel: mma8452: improve coding style, pm and resource cleanup Sanjay Chitroda
2026-04-22 16:56 ` [PATCH v2 1/6] iio: accel: mma8452: cleanup codestyle warning Sanjay Chitroda
2026-04-22 16:56 ` [PATCH v2 2/6] iio: accel: mma8452: sort headers alphabetically Sanjay Chitroda
2026-04-22 19:30 ` Andy Shevchenko
2026-04-23 2:30 ` Sanjay Chitroda
2026-04-22 16:56 ` [PATCH v2 3/6] iio: accel: mma8452: use local struct device Sanjay Chitroda
2026-04-22 19:35 ` Andy Shevchenko
2026-04-23 2:36 ` Sanjay Chitroda [this message]
2026-04-22 16:56 ` [PATCH v2 4/6] iio: accel: mma8452: Use dev_err_probe() Sanjay Chitroda
2026-04-22 19:37 ` Andy Shevchenko
2026-04-22 16:56 ` [PATCH v2 5/6] iio: accel: mma8452: use pm_ptr() for dev_pm_ops Sanjay Chitroda
2026-04-22 19:38 ` Andy Shevchenko
2026-04-22 16:56 ` [PATCH v2 6/6] iio: accel: mma8452: use guard() to release mutexes Sanjay Chitroda
2026-04-22 19:40 ` Andy Shevchenko
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=BA5F2EF9-C439-47A2-BE91-4ED6E12F2EBA@gmail.com \
--to=sanjayembeddedse@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=sakari.ailus@linux.intel.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