From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Akshay Jindal <akshayaj.lkd@gmail.com>,
anshulusr@gmail.com, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, shuah@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7] iio: light: ltr390: Implement runtime PM support
Date: Sat, 13 Sep 2025 13:17:24 +0100 [thread overview]
Message-ID: <20250913131724.111fa939@jic23-huawei> (raw)
In-Reply-To: <CAHp75Vf+9PJgR5Eev_Z+QB4cp+VMctFfqpTMWuE3VsnGpZ6dJQ@mail.gmail.com>
On Wed, 10 Sep 2025 23:24:22 +0300
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Wed, Sep 10, 2025 at 10:12 PM Jonathan Cameron <jic23@kernel.org> wrote:
> > On Wed, 10 Sep 2025 18:06:32 +0530
> > Akshay Jindal <akshayaj.lkd@gmail.com> wrote:
>
> > > Thank you very much for your valuable feedback.
> > > I do have a small request regarding the review process. Over the past 3–4
> > > versions,most of the comments have been about fixing indentations and
> > > improving code readability. I would kindly request if it would be possible
> > > to consolidate such cosmetic comments into a single review round.
> > >
> > > I completely understand that incremental feedback makes sense when the code
> > > is actively changing, but if the changes are minimal, spreading out minor
> > > suggestions over multiple review cycles tends to unnecessarily increase the
> > > turnaround time.
> > >
> > > Your support in this would help me address the comments more efficiently.
>
> I can't always see _all_ problems at once, I am not a robot. I will
> try my best, though.
>
> ...
>
> > Andy, if you are fine with the explanation I'll tidy up the minor stuff
> > whilst applying.
>
> Yes, I am fine, go with it, thanks!
>
Applied with this diff;
diff --git a/drivers/iio/light/ltr390.c b/drivers/iio/light/ltr390.c
index 2d8449aeab18..a2b804e9089a 100644
--- a/drivers/iio/light/ltr390.c
+++ b/drivers/iio/light/ltr390.c
@@ -284,8 +284,8 @@ static int ltr390_do_read_raw(struct iio_dev *iio_device,
}
static int ltr390_read_raw(struct iio_dev *iio_device,
- struct iio_chan_spec const *chan, int *val,
- int *val2, long mask)
+ struct iio_chan_spec const *chan,
+ int *val, int *val2, long mask)
{
int ret;
struct ltr390_data *data = iio_priv(iio_device);
@@ -749,7 +749,7 @@ static void ltr390_powerdown(void *priv)
dev_err(dev, "failed to disable interrupts\n");
data->irq_enabled = false;
- pm_runtime_put_autosuspend(&data->client->dev);
+ pm_runtime_put_autosuspend(dev);
}
ret = regmap_clear_bits(data->regmap, LTR390_MAIN_CTRL, LTR390_SENSOR_ENABLE);
Thanks,
Jonathan
next prev parent reply other threads:[~2025-09-13 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 19:46 [PATCH v7] iio: light: ltr390: Implement runtime PM support Akshay Jindal
2025-09-10 7:17 ` Andy Shevchenko
2025-09-10 11:02 ` Jonathan Cameron
2025-09-10 18:00 ` Akshay Jindal
2025-09-10 18:52 ` Jonathan Cameron
2025-09-10 12:36 ` Akshay Jindal
2025-09-10 19:12 ` Jonathan Cameron
2025-09-10 20:24 ` Andy Shevchenko
2025-09-13 12:17 ` Jonathan Cameron [this message]
2025-09-13 15:58 ` Akshay Jindal
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=20250913131724.111fa939@jic23-huawei \
--to=jic23@kernel.org \
--cc=akshayaj.lkd@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=anshulusr@gmail.com \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=shuah@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