From: sashiko-bot@kernel.org
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v1 2/4] ACPI: Drop unused .driver_data initializers in acpi_device_id arrays
Date: Fri, 13 Nov 2026 11:17:45 +0000 [thread overview]
Message-ID: <sashiko-outbox-212696@kernel.org> (raw)
In-Reply-To: <b7c5533882b5a979a4ba19a87e9ba1b13a24023d.1794567577.git.ukleinek@kernel.org>
> From: Uwe Kleine-König (The Capable Hub) <ukleinek@kernel.org>
>
> Many drivers explicitly initialize the .driver_data member in their
> acpi_device_id arrays without actually using that value. Drop these
> assignments and while touching these lines use named initializers for
> .id and use consistent spacing.
>
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1794567577.git.ukleinek@kernel.org?part=2
next prev parent reply other threads:[~2026-11-13 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 11:13 [PATCH v1 0/4] ACPI: Use named initializers for acpi_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-11-13 11:13 ` [PATCH v1 1/4] ACPI: Unify acpi_device_id list terminators Uwe Kleine-König (The Capable Hub)
2026-11-13 11:20 ` sashiko-bot
2026-11-13 11:13 ` [PATCH v1 2/4] ACPI: Drop unused .driver_data initializers in acpi_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-11-13 11:17 ` sashiko-bot [this message]
2026-11-13 11:13 ` [PATCH v1 3/4] ACPI: Use named initializers for " Uwe Kleine-König (The Capable Hub)
2026-11-13 11:14 ` [PATCH v1 4/4] ACPI: Unify *_device_id list terminators Uwe Kleine-König (The Capable Hub)
2026-11-13 11:20 ` 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=sashiko-outbox-212696@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-pci@vger.kernel.org \
--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.