From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: sashiko-reviews@lists.linux.dev
Cc: Frank.Li@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v1 4/6] power: Use named initializers for platform_device_id arrays
Date: Fri, 26 Jun 2026 15:58:19 +0200 [thread overview]
Message-ID: <aj6EzGn2Ds2offEc@monoceros> (raw)
In-Reply-To: <20260529110229.9474D1F00893@smtp.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1661 bytes --]
On Fri, May 29, 2026 at 11:02:29AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] The explicit `.driver_data` initialization `TYPE_MAX8998` for `max8998-battery` was silently dropped without mention in the commit message.
> --
>
> commit 02f2c38ebeef8dff34934050c70916818fb36a18
> Author: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
>
> power: Use named initializers for platform_device_id arrays
>
> This commit updates various power supply and reset drivers to use named
> initializers for platform_device_id arrays. It also unifies spacing and
> comma usage across these array definitions.
>
> > diff --git a/drivers/power/supply/max8998_charger.c b/drivers/power/supply/max8998_charger.c
> > index 418b882b163d1..b0eda2b51e7f0 100644
> > --- a/drivers/power/supply/max8998_charger.c
> > +++ b/drivers/power/supply/max8998_charger.c
> > @@ -188,7 +188,7 @@ static int max8998_battery_probe(struct platform_device *pdev)
> > }
> >
> > static const struct platform_device_id max8998_battery_id[] = {
> > - { "max8998-battery", TYPE_MAX8998 },
> > + { .name = "max8998-battery" },
>
> [Severity: Low]
> Is it intentional that the TYPE_MAX8998 driver data assignment was dropped
> here?
Yes, it was intentional, but that change doesn't fit to the commit log.
The driver doesn't use the value in .driver_data, so the change is fine
in principle. Given that the patch was already applied, I think it's
fine to keep it as is, but of course I'm open to respin with that detail
fixed.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-06-26 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 10:18 [PATCH v1 0/6] power: Use named initializers for platform_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-05-29 10:18 ` [PATCH v1 4/6] " Uwe Kleine-König (The Capable Hub)
2026-05-29 11:02 ` sashiko-bot
2026-06-26 13:58 ` Uwe Kleine-König [this message]
2026-05-29 11:29 ` Joshua Peisach
2026-05-29 18:49 ` Uwe Kleine-König (The Capable Hub)
2026-06-01 6:48 ` Matti Vaittinen
2026-06-03 20:46 ` (subset) [PATCH v1 0/6] " Sebastian Reichel
2026-06-26 8:20 ` patchwork-bot+linux-riscv
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=aj6EzGn2Ds2offEc@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=Frank.Li@kernel.org \
--cc=imx@lists.linux.dev \
--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