From: sashiko-bot@kernel.org
To: "Roman Vivchar" <rva333@protonmail.com>
Cc: dri-devel@lists.freedesktop.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
lee@kernel.org
Subject: Re: [PATCH v2 2/2] backlight: add ktd3137 support
Date: Tue, 10 Nov 2026 19:49:10 +0000 [thread overview]
Message-ID: <sashiko-outbox-207683@kernel.org> (raw)
In-Reply-To: <20261110-6768-ktd3137-v2-2-9496c51efea4@protonmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] backlight: ktd3137: use named initializer in ktd3137_ids
--
commit 8835810206d0f5ccda9a816dd64ce8c1128ef9b3
Author: Roman Vivchar <rva333@protonmail.com>
backlight: add ktd3137 support
This commit adds an I2C backlight driver for the Kinetic KTD3137 display
backlight IC.
> diff --git a/drivers/video/backlight/ktd3137.c b/drivers/video/backlight/ktd3137.c
> new file mode 100644
> index 0000000000000..1595aefd46e6c
> --- /dev/null
> +++ b/drivers/video/backlight/ktd3137.c
> @@ -0,0 +1,258 @@
[ ... ]
> +static const struct i2c_device_id ktd3137_ids[] = {
> + { "ktd3137" },
> + { }
> +};
[Severity: Low]
This isn't a bug, but new struct i2c_device_id entries should use named
initializers ({ .name = "ktd3137" }).
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110-6768-ktd3137-v2-0-9496c51efea4@protonmail.com?part=2
prev parent reply other threads:[~2026-11-10 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 19:38 [PATCH v2 0/2] backlight: add ktd3137 support Roman Vivchar via B4 Relay
2026-11-10 19:38 ` [PATCH v2 1/2] dt-bindings: leds: backlight: add Kinetic KTD3137 Roman Vivchar via B4 Relay
2026-11-11 12:11 ` Krzysztof Kozlowski
2026-11-10 19:38 ` [PATCH v2 2/2] backlight: add ktd3137 support Roman Vivchar via B4 Relay
2026-11-10 19:49 ` sashiko-bot [this message]
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=sashiko-outbox-207683@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rva333@protonmail.com \
--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