From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: sashiko-reviews@lists.linux.dev
Cc: Frank.Li@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v1 07/20] gpio: Add missing OF module annotations
Date: Tue, 14 Jul 2026 10:09:34 +0200 [thread overview]
Message-ID: <alXtMOwKmsfM0LDE@monoceros> (raw)
In-Reply-To: <20260714073425.CA6181F000E9@smtp.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]
Hello,
On Tue, Jul 14, 2026 at 07:34:25AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
>
> Pre-existing issues:
> - [High] Missing MODULE_DEVICE_TABLE export for the mpc52xx_simple_gpiochip_match table.
> --
>
> --- Patch [7]: [PATCH v1 07/20] gpio: Add missing OF module annotations ---
> commit 292bbbdcede3ce86fe1309d514a852f272c27bac
> Author: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
>
> gpio: Add missing OF module annotations
>
> A driver module matching devices using an of device id table is supposed
> to declare that in the module's metadata. Add this information for
> several drivers that failed to declare these.
>
> [ ... ]
>
> > diff --git a/drivers/gpio/gpio-mpc5200.c b/drivers/gpio/gpio-mpc5200.c
> > index 00f209157fd0f..2c828bc922ae3 100644
> > --- a/drivers/gpio/gpio-mpc5200.c
> > +++ b/drivers/gpio/gpio-mpc5200.c
> > @@ -180,6 +180,7 @@ static const struct of_device_id mpc52xx_wkup_gpiochip_match[] = {
> > { .compatible = "fsl,mpc5200-gpio-wkup", },
> > {}
> > };
> > +MODULE_DEVICE_TABLE(of, mpc52xx_wkup_gpiochip_match);
> >
> > static struct platform_driver mpc52xx_wkup_gpiochip_driver = {
> > .driver = {
>
> [Severity: High]
> This isn't a bug introduced by this patch, but since the patch focuses on
> adding missing OF module annotations, should it also add one for the second
> match table in this same file?
Ah, this is snaky, there are two drivers in that file and thus two
of_device_id arrays. My script only handles the first, so the style fixes
are missing here, too.
I will wait a bit for further review and then address this in a v2.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-07-14 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 7:24 [PATCH v1 00/20] gpio: Improvements around device-id arrays Uwe Kleine-König (The Capable Hub)
2026-07-14 7:24 ` [PATCH v1 07/20] gpio: Add missing OF module annotations Uwe Kleine-König (The Capable Hub)
2026-07-14 7:34 ` sashiko-bot
2026-07-14 8:09 ` Uwe Kleine-König (The Capable Hub) [this message]
2026-07-14 13:55 ` Daniel Palmer
2026-07-24 7:24 ` Linus Walleij
2026-07-24 15:32 ` Frank Li
2026-07-14 7:24 ` [PATCH v1 16/20] gpio: Unify style of of_device_id arrays Uwe Kleine-König (The Capable Hub)
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=alXtMOwKmsfM0LDE@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