public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts via B4 Relay <devnull+joshua.crofts1.gmail.com@kernel.org>
Cc: joshua.crofts1@gmail.com, "David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Jean-Francois Dagenais" <jeff.dagenais@gmail.com>,
	"Maxime Roussin-Bélanger" <maxime.roussinbelanger@gmail.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	sashiko-bot <sashiko-bot@kernel.org>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v5 0/8] iio: light: si1133: driver cleanup
Date: Tue, 5 May 2026 13:34:43 +0100	[thread overview]
Message-ID: <20260505133443.4e345627@jic23-huawei> (raw)
In-Reply-To: <20260505-si1133-checkup-v5-0-5df86a9024ed@gmail.com>

On Tue, 05 May 2026 09:31:25 +0200
Joshua Crofts via B4 Relay <devnull+joshua.crofts1.gmail.com@kernel.org> wrote:

> This series deals with the cleanup and modernization of the Silicon
> Labs SI1133 UV/Ambient light sensor.
> 
> What seemed like a simple checkpatch cleanup turned out to be more
> complex, therefore I've ended up doing a patch series instead.
> 
> Changes include:
>  - adding missing headers
>  - removing unused macros
>  - adding guard(mutex)() support
>  - code style fixes
>  - race condition fixes reported by Sashiko
> 
> Signed-off-by: Joshua Crofts <joshua.crofts1@gmail.com>
Applied.

Sashiko is far from happy but I think what it is picking up on
are either wrong (like the i2c stuff) or about other potential issues
in the driver.

Correctly recovering from every error case is fine so I tend
to think of that as best effort only rather than worrying too much
about the more complex parts.

So applied with that one tweak to where timeout is assigned in patch 7.

Thanks,

Jonathan

> ---
> Changes in v5:
> - PATCH 5: fix commit message
> - Pick up Andy's Reviewed-by tag
> - Link to v4: https://lore.kernel.org/r/20260430-si1133-checkup-v4-0-fb3e9dce41bf@gmail.com
> 
> Changes in v4:
> - Changed logical ordering of patchset
> - PATCH 1: fix typo in comment, edit commit message
> - PATCH 2: edit commit message
> - PATCH 3: edit commit message
> - PATCH 5: remove irqreturn.h and add mod_devicetable.h
> - Link to v3: https://lore.kernel.org/r/20260429-si1133-checkup-v3-0-469f21d960eb@gmail.com
> 
> Changes in v3:
> - PATCH 6: add local variable for timeout
> - PATCH 7 & 8: fix potential race conditions as pointed out by Sashiko
> - Link to v2: https://lore.kernel.org/r/20260428-si1133-checkup-v2-0-70ad14bfefe2@gmail.com
> 
> Changes in v2:
> - Change v2 to patch series
> - PATCH 2: remove unused macros
> - PATCH 3: add missing include headers
> - PATCH 4: group generic <linux/*> headers
> - PATCH 5: add guard(mutex)() support
> - Link to v1: https://lore.kernel.org/r/20260427-si1133-checkup-v1-1-20f5f11eba6c@gmail.com
> 
> ---
> Joshua Crofts (8):
>       iio: light: si1133: reset counter to prevent race condition
>       iio: light: si1133: prevent race condition on timeout
>       iio: light: si1133: remove unused macros
>       iio: light: si1133: prefer complex macros enclosed in parenthesis
>       iio: light: si1133: add missing include headers
>       iio: light: si1133: group generic <linux/*> headers
>       iio: light: si1133: add local variable for timeout
>       iio: light: si1133: use guard(mutex)() macro
> 
>  drivers/iio/light/si1133.c | 69 +++++++++++++++++++++++++++-------------------
>  1 file changed, 41 insertions(+), 28 deletions(-)
> ---
> base-commit: d86db1905add39f905cf9f04252804b359914ed6
> change-id: 20260427-si1133-checkup-abcc5280adf3
> 
> Best regards,


  parent reply	other threads:[~2026-05-05 12:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  7:31 [PATCH v5 0/8] iio: light: si1133: driver cleanup Joshua Crofts via B4 Relay
2026-05-05  7:31 ` [PATCH v5 1/8] iio: light: si1133: reset counter to prevent race condition Joshua Crofts via B4 Relay
2026-05-05  7:31 ` [PATCH v5 2/8] iio: light: si1133: prevent race condition on timeout Joshua Crofts via B4 Relay
2026-05-05  7:31 ` [PATCH v5 3/8] iio: light: si1133: remove unused macros Joshua Crofts via B4 Relay
2026-05-05  7:31 ` [PATCH v5 4/8] iio: light: si1133: prefer complex macros enclosed in parenthesis Joshua Crofts via B4 Relay
2026-05-05  7:31 ` [PATCH v5 5/8] iio: light: si1133: add missing include headers Joshua Crofts via B4 Relay
2026-05-05  7:31 ` [PATCH v5 6/8] iio: light: si1133: group generic <linux/*> headers Joshua Crofts via B4 Relay
2026-05-05  7:31 ` [PATCH v5 7/8] iio: light: si1133: add local variable for timeout Joshua Crofts via B4 Relay
2026-05-05 12:30   ` Jonathan Cameron
2026-05-05  7:31 ` [PATCH v5 8/8] iio: light: si1133: use guard(mutex)() macro Joshua Crofts via B4 Relay
2026-05-05 12:34 ` Jonathan Cameron [this message]
2026-05-05 14:05   ` [PATCH v5 0/8] iio: light: si1133: driver cleanup Joshua Crofts

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=20260505133443.4e345627@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=devnull+joshua.crofts1.gmail.com@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jeff.dagenais@gmail.com \
    --cc=joshua.crofts1@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.roussinbelanger@gmail.com \
    --cc=nuno.sa@analog.com \
    --cc=sashiko-bot@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