From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Markus Schneider-Pargmann <msp@baylibre.com>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] parport: Consistently define pci_device_ids using named initializers
Date: Fri, 17 Jul 2026 12:26:36 +0200 [thread overview]
Message-ID: <aloC8ztBlWm8FObP@monoceros> (raw)
In-Reply-To: <aimV1vrFax7s3Ins@monoceros>
[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]
Hello,
On Wed, Jun 10, 2026 at 06:54:02PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> [adding Greg to Cc: as his tree seems to be the usual way into mainline
> for these drivers.]
>
> Hello Sudip,
>
> On Wed, Apr 29, 2026 at 06:14:53PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> > ... and PCI device helpers.
> >
> > The various struct pci_device_id arrays were initialized mostly by list
> > expressions. This isn't easily readable if you're not into PCI.
> >
> > Use PCI_DEVICE* helper macros and named initializers which is more
> > explicit and thus easier to parse. Also skip explicit assignments of 0
> > (which the compiler then takes care of).
> >
> > 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>
>
> Gentil ping! I'd like to work on the actual change to pci_device_id and
> that requires this patch to be in.
>
> Is it already too late for 7.2-rc1?
Now (i.e. 5 weeks later) it definitively is too late for it to make it
into v7.2-rc1.
What does it need that this patch is picked up?
There is also
https://lore.kernel.org/lkml/549d7f4d912e7c38bb93f0c40844fae291dac532.1781101238.git.u.kleine-koenig@baylibre.com/
in my list of open patches affecting parport.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-07-17 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 16:14 Uwe Kleine-König (The Capable Hub)
2026-06-10 16:53 ` Uwe Kleine-König (The Capable Hub)
2026-07-17 10:26 ` Uwe Kleine-König (The Capable Hub) [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=aloC8ztBlWm8FObP@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=sudipm.mukherjee@gmail.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
Powered by JetHome