From: sashiko-bot@kernel.org
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: Frank.Li@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v2 6/6] ASOC: Unify code style for platform_device_id arrays
Date: Mon, 20 Jul 2026 06:29:06 +0000 [thread overview]
Message-ID: <20260720062907.173371F000E9@smtp.kernel.org> (raw)
In-Reply-To: <093867d47c079d2aaab06bccaae734c54c342a7d.1784528081.git.u.kleine-koenig@baylibre.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The commit introduces a style inconsistency by missing several small platform_device_id arrays during its mechanical refactoring, despite the commit message claiming to use a 'compact one-line style for small entries'.
--
--- Patch [6]: [PATCH v2 6/6] ASOC: Unify code style for platform_device_id arrays ---
commit 03434ab8a73c8818fd87d755c26c0b8e9e4f5807
Author: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
ASOC: Unify code style for platform_device_id arrays
This commit unifies the code style of platform_device_id arrays across
various ASoC drivers. It updates list terminators to use a single space and
attempts to use a compact one-line style for small entries.
[ ... ]
> diff --git a/sound/soc/intel/avs/boards/probe.c b/sound/soc/intel/avs/boards/probe.c
> index 73884f8a535ca..4053d14289b95 100644
> --- a/sound/soc/intel/avs/boards/probe.c
> +++ b/sound/soc/intel/avs/boards/probe.c
> @@ -64,7 +64,7 @@ static const struct platform_device_id avs_probe_mb_driver_ids[] = {
> {
> .name = "avs_probe_mb",
> },
> - {},
> + { }
[Severity: Low]
This isn't a bug, but should this entry also use the compact one-line style
mentioned in the commit message? It seems like this array missed the single
line styling update that was applied to files like da7219.c.
> };
> MODULE_DEVICE_TABLE(platform, avs_probe_mb_driver_ids);
[ ... ]
> diff --git a/sound/soc/intel/avs/boards/rt274.c b/sound/soc/intel/avs/boards/rt274.c
> index a689f4c80867b..289f1230851f4 100644
> --- a/sound/soc/intel/avs/boards/rt274.c
> +++ b/sound/soc/intel/avs/boards/rt274.c
> @@ -261,7 +261,7 @@ static const struct platform_device_id avs_rt274_driver_ids[] = {
> {
> .name = "avs_rt274",
> },
> - {},
> + { }
[Severity: Low]
This isn't a bug, but similar to the probe.c file above, should this entry
be compacted to a single line? There are several other files in this
directory (rt286.c, rt298.c, rt5514.c, etc.) that also seem to have missed
the compact one-line style update.
> };
> MODULE_DEVICE_TABLE(platform, avs_rt274_driver_ids);
>
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1784528081.git.u.kleine-koenig@baylibre.com?part=6
prev parent reply other threads:[~2026-07-20 6:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 6:23 [PATCH v2 0/6] ASoC: Use named initializers for platform_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-07-20 6:23 ` [PATCH v2 1/6] ASoC: codecs: mt6357: Drop unused assignment of platform_device_id driver data Uwe Kleine-König (The Capable Hub)
2026-07-20 6:23 ` [PATCH v2 2/6] ASoC: renesas: fsi: Drop platform probing metadata Uwe Kleine-König (The Capable Hub)
2026-07-20 23:12 ` Kuninori Morimoto
2026-07-20 6:23 ` [PATCH v2 3/6] ASoC: amd: acp: Use named initializers for platform_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-07-21 3:48 ` Mukunda,Vijendar
2026-07-20 6:23 ` [PATCH v2 4/6] ASoC: amd: acp: Unify code style for platform_device_id array Uwe Kleine-König (The Capable Hub)
2026-07-20 7:05 ` Cezary Rojewski
2026-07-20 11:32 ` Uwe Kleine-König (The Capable Hub)
2026-07-21 3:49 ` Mukunda,Vijendar
2026-07-20 6:23 ` [PATCH v2 5/6] ASoC: Use named initializers for platform_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-07-20 8:23 ` Charles Keepax
2026-07-20 6:23 ` [PATCH v2 6/6] ASOC: Unify code style " Uwe Kleine-König (The Capable Hub)
2026-07-20 6:29 ` 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=20260720062907.173371F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=imx@lists.linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
--cc=u.kleine-koenig@baylibre.com \
/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.