From: sashiko-bot@kernel.org
To: "Ahmad Byagowi" <ahmadexp@gmail.com>
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
conor+dt@kernel.org, lee@kernel.org, robh@kernel.org
Subject: Re: [RFC net-next 2/4] leds: rgb: Add IS32FL3207 controller driver
Date: Mon, 03 Aug 2026 15:46:43 +0000 [thread overview]
Message-ID: <20260803154644.9626E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <7daca0186b6906af1d57314eebcecffc4cb68063.1785684064.git.ahmadexp@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The i2c_device_id array is initialized without named initializers.
--
--- Patch [2]: [RFC net-next 2/4] leds: rgb: Add IS32FL3207 controller driver ---
commit 2f0ef1606e8fe9f37cd22e9360f765264557dd4d
Author: Ahmad Byagowi <ahmadexp@gmail.com>
leds: rgb: Add IS32FL3207 controller driver
This commit adds a generic I2C driver for the Lumissil IS32FL3207 18-channel
LED controller. It exposes individual and multicolor LEDs through the LED
class, handling optional supply and enable GPIO.
> diff --git a/drivers/leds/rgb/leds-is32fl3207.c b/drivers/leds/rgb/leds-is32fl3207.c
> new file mode 100644
> index 0000000000000..8f04534644dce
> --- /dev/null
> +++ b/drivers/leds/rgb/leds-is32fl3207.c
[ ... ]
> +static const struct of_device_id is32fl3207_of_match[] = {
> + { .compatible = "issi,is32fl3207" },
> + { }
> +};
> +MODULE_DEVICE_TABLE(of, is32fl3207_of_match);
> +
> +static const struct i2c_device_id is32fl3207_id[] = {
> + { "is32fl3207" },
[Severity: Low]
This isn't a bug, but should this array use a named initializer
(e.g., { .name = "is32fl3207" })? The I2C subsystem guidelines request
that initialized arrays of type struct i2c_device_id use named initializers.
> + { }
> +};
> +MODULE_DEVICE_TABLE(i2c, is32fl3207_id);
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1785684064.git.ahmadexp@gmail.com?part=2
next prev parent reply other threads:[~2026-08-03 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 15:46 [RFC net-next 0/4] ptp: ocp: Add R4006 I2C peripheral support Ahmad Byagowi
2026-08-02 15:46 ` [RFC net-next 1/4] dt-bindings: leds: Add IS32FL3207 controller Ahmad Byagowi
2026-08-03 15:46 ` sashiko-bot
2026-08-02 15:46 ` [RFC net-next 2/4] leds: rgb: Add IS32FL3207 controller driver Ahmad Byagowi
2026-08-03 15:46 ` sashiko-bot [this message]
2026-08-02 15:46 ` [RFC net-next 3/4] i2c: mux: Propagate software nodes to channel adapters Ahmad Byagowi
2026-08-03 15:46 ` sashiko-bot
2026-08-02 15:46 ` [RFC net-next 4/4] ptp: ocp: Add R4006 I2C peripheral topology Ahmad Byagowi
2026-08-03 15:46 ` sashiko-bot
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=20260803154644.9626E1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ahmadexp@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox