From: Jonathan Cameron <jic23@kernel.org>
To: Aldo Conte <aldocontelk@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
shuah@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH v2 5/5] iio: light: tcs3472: move standalone return to default case
Date: Sat, 16 May 2026 13:25:55 +0100 [thread overview]
Message-ID: <20260516132555.64e27d62@jic23-huawei> (raw)
In-Reply-To: <1c87362a-bba8-45b8-a836-153f468815c4@gmail.com>
On Sat, 16 May 2026 13:04:13 +0200
Aldo Conte <aldocontelk@gmail.com> wrote:
> On 15/05/26 20:05, Jonathan Cameron wrote:
> > On Wed, 13 May 2026 20:58:40 +0300
> > Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
>
> ...
>
> >
> > I would add for this that, to reduce churn it's fine to add the
> > struct device *dev = ... bit and use it in new devm calls. Just do the
> > remainder in the follow on commit.
> >
> >>
> >>
> >
>
> Hi Jonathan, Andy and all!
>
> Thanks for your reviews! they’re teaching me so much!
> If I understand correctly, I need to wait a week before submitting version v3
> such that other reviewers can comment right?
>
> I’d like to take this opportunity to suggest two alternative lists of what
> version v3 might look like in terms of patch order:
>
> First option does not consider the "== NULL with !" patch and so:
> 1. iio: tcs3472: power down chip on probe failure (NEW precursor, bug fix)
> 2. iio: tcs3472: sort headers alphabetically (same)
> 3. iio: tcs3472: convert several functions to use guard(mutex)() (modified)
> 4. iio: tcs3472: use devm for resource management (slimmed down)
> 5. iio: tcs3472: use locale struct device * for remaining cases (NEW)
> 6. iio: tcs3472: implement wait time and sampling frequency (revised)
> 7. iio: tcs3472: move standalone return to default case (same as v2)
>
> Second version will consider it:
> 1. iio: tcs3472: power down chip on probe failure (NEW precursor, bug fix)
> 2. iio: tcs3472: sort headers alphabetically (same as v2)
> 3. iio: tcs3472: convert several functions to use guard(mutex)() (modified)
> 4. iio: tcs3472: replace == NULL with ! (NEW, optional)
> 5. iio: tcs3472: use devm for resource management (slimmed down)
> 6. iio: tcs3472: use locale struct device * for remaining cases (NEW)
> 7. iio: tcs3472: implement wait time and sampling frequency (revised)
> 8. iio: tcs3472: move standalone return to default case (same as v2)
>
>
> What do you think?
Either is fine but swap the last two patches. The wait time one is
more complex than that trivial cleanup so might take more revisions.
I frequently pick up the first part of series just to avoid people
having to keep sending the same unchanged code to the list (that I've
often forgotten about completely by the next version!)
Jonathan
>
>
> Thanks,
> Aldo
next prev parent reply other threads:[~2026-05-16 12:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 22:32 [PATCH v2 0/5] devm conversion, wait time, locking cleanup Aldo Conte
2026-05-12 22:32 ` [PATCH v2 1/5] iio: light: tcs3472: sort headers alphabetically Aldo Conte
2026-05-13 8:15 ` Joshua Crofts
2026-05-12 22:32 ` [PATCH v2 2/5] iio: light: tcs3472: convert remaining locking to guard(mutex) Aldo Conte
2026-05-13 7:47 ` Joshua Crofts
2026-05-13 11:00 ` Andy Shevchenko
2026-05-13 10:58 ` Andy Shevchenko
2026-05-15 15:18 ` Jonathan Cameron
2026-05-12 22:32 ` [PATCH v2 3/5] iio: light: tcs3472: use devm for resource management Aldo Conte
2026-05-13 8:07 ` Joshua Crofts
2026-05-13 11:02 ` Andy Shevchenko
2026-05-13 20:29 ` Aldo Conte
2026-05-15 15:21 ` Jonathan Cameron
2026-05-15 17:19 ` Jonathan Cameron
2026-05-12 22:32 ` [PATCH v2 4/5] iio: light: tcs3472: implement wait time and sampling frequency Aldo Conte
2026-05-13 11:17 ` Andy Shevchenko
2026-05-15 15:57 ` Aldo Conte
2026-05-15 18:01 ` Jonathan Cameron
2026-05-12 22:32 ` [PATCH v2 5/5] iio: light: tcs3472: move standalone return to default case Aldo Conte
2026-05-13 8:16 ` Joshua Crofts
2026-05-13 11:23 ` Andy Shevchenko
2026-05-13 16:12 ` Aldo Conte
2026-05-13 17:58 ` Andy Shevchenko
2026-05-15 18:05 ` Jonathan Cameron
2026-05-16 11:04 ` Aldo Conte
2026-05-16 12:25 ` Jonathan Cameron [this message]
2026-05-15 15:11 ` [PATCH v2 0/5] devm conversion, wait time, locking cleanup Jonathan Cameron
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=20260516132555.64e27d62@jic23-huawei \
--to=jic23@kernel.org \
--cc=aldocontelk@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--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