From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: linux-pwm@vger.kernel.org
Cc: Markus Schneider-Pargmann <msp@baylibre.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pwm: Consistently define pci_device_ids using named initializers
Date: Thu, 7 May 2026 17:10:49 +0200 [thread overview]
Message-ID: <afyrQ9_saRlKv-Fi@monoceros> (raw)
In-Reply-To: <20260504085535.1914668-2-u.kleine-koenig@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
Hello,
On Mon, May 04, 2026 at 10:55:35AM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> The .driver_data member in the various struct pci_device_id arrays were
> initialized by list expressions. This isn't easily readable if you're
> not into PCI. Using named initializers is more explicit and thus easier
> to parse.
>
> The secret plan is to make struct pci_device_id::driver_data an
> anonymous union (similar to
> https://lore.kernel.org/all/cover.1776579304.git.u.kleine-koenig@baylibre.com/)
> and that requires named initializers. But it's also a nice cleanup on
> its own.
>
> This change doesn't introduce changes to the compiled pci_device_id
> arrays. Tested on x86 and arm64.
>
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git pwm/for-next
.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
parent reply other threads:[~2026-05-07 15:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260504085535.1914668-2-u.kleine-koenig@baylibre.com>]
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=afyrQ9_saRlKv-Fi@monoceros \
--to=ukleinek@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=msp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox