All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Alban Bedel" <alban.bedel@lht.dlh.de>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/2] gpio: Support ON Semi CAT9532
Date: Tue, 15 Sep 2026 09:31:51 +0000	[thread overview]
Message-ID: <20260915093152.367111F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260915092046.931449-3-alban.bedel@lht.dlh.de>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] i2c: i2c_device_id array missing named initializers
--

commit ce4c104d77312ee9164e59bc58ade163f20cd3c0
Author: Alban Bedel <alban.bedel@lht.dlh.de>

gpio: Support ON Semi CAT9532
    
This commit adds support for the CAT9532 LED dimmer from On Semiconductor,
implementing it as an open-drain GPIO controller driver.

> diff --git a/drivers/gpio/gpio-cat9532.c b/drivers/gpio/gpio-cat9532.c
> new file mode 100644
> index 0000000000000..973ff74a15b89
> --- /dev/null
> +++ b/drivers/gpio/gpio-cat9532.c

[ ... ]

> +static const struct i2c_device_id cat9532_i2c_id[] = {
> +	{ "cat9532" },

[Severity: Low]
This isn't a bug, but does this array initialization in cat9532_i2c_id
violate the I2C subsystem rule requiring named initializers for
struct i2c_device_id? 

Using positional initialization like { "cat9532" } instead of
{ .name = "cat9532" } goes against the documented subsystem style guidelines.

> +	{ },
> +};
> +MODULE_DEVICE_TABLE(i2c, cat9532_i2c_id);

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260915092046.931449-1-alban.bedel@lht.dlh.de?part=2

  reply	other threads:[~2026-09-15  9:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  9:20 [PATCH 0/2] Support ON Semi CAT9532 Alban Bedel
2026-09-15  9:20 ` [PATCH 1/2] dt-bindings: gpio: Add CAT9532 GPIO Alban Bedel
2026-09-15  9:30   ` sashiko-bot
2026-09-15  9:43   ` Linus Walleij
2026-09-15  9:47   ` Linus Walleij
2026-09-15 16:42   ` Conor Dooley
2026-09-15  9:20 ` [PATCH 2/2] gpio: Support ON Semi CAT9532 Alban Bedel
2026-09-15  9:31   ` sashiko-bot [this message]
2026-09-15  9:51   ` Bartosz Golaszewski
2026-09-15  9:57     ` Bartosz Golaszewski
2026-09-15 13:48       ` Alban Bedel
2026-09-16  9:07         ` Bartosz Golaszewski
2026-09-15  9:59   ` Linus Walleij

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=20260915093152.367111F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=alban.bedel@lht.dlh.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.