From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Lee Jones <lee@kernel.org>,
David Rhodes <david.rhodes@cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Zha Qipeng <qipeng.zha@intel.com>,
Qunqin Zhao <zhaoqunqin@loongson.cn>,
Thomas Richard <thomas.richard@bootlin.com>,
linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
mfd@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Linus Walleij <linusw@kernel.org>,
Pawel Zalewski <pzalewski@thegoodpenguin.co.uk>
Subject: Re: [PATCH v4 10/20] mfd: Use named initializers for acpi_device_id arrays
Date: Wed, 11 Nov 2026 10:55:34 +0100 [thread overview]
Message-ID: <avQ19KBnQ2mnhZa-@monoceros> (raw)
In-Reply-To: <avQrO4etMgpOhvwF@ashevche-desk.local>
[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]
[adding Pawel to Cc:]
Hello Andy,
On Wed, Nov 11, 2026 at 10:45:47AM +0200, Andy Shevchenko wrote:
> On Tue, Nov 10, 2026 at 10:54:35PM +0100, Uwe Kleine-König (The Capable Hub) wrote:
> > While being less compact, using named initializers allows to more easily
> > see which members of the structs are assigned which value without having
> > to lookup the declaration of the struct. And it's also more robust
> > against changes to the struct definition.
> >
> > The mentioned robustness is relevant for a planned change to struct
> > acpi_device_id that replaces .driver_data by an anonymous union.
> >
> > This patch doesn't modify the compiled arrays, only their representation
> > in source form benefits.
>
> I don't know who is the first, you, guys, collaborate together and come up with
> a solution, but I have reviewed already this
> https://lore.kernel.org/lkml/20261104-acpi-mfd-v2-0-64b9dee3baaf@thegoodpenguin.co.uk/
Oh, I wasn't aware that Pawel is still on that. Initially we had a list
where Pawel indeed was assigned for acpi_device_id. Since then I went on
to do these changes per subsystem for several *_device_id at once
(instead of per *_device_id and subsystem) and stopped looking after the
initial list. I might have mentioned that in our internal chat, but I
take the blame on the lack of coordination.
Looking through the differences I found:
- different commit log
- I have a cleanup to drivers/mfd/kempld-core.c which conflicts with
Pawel's series
@Lee: If you take Pawel's series, I can rebase and resend. Most of my
patches still apply just fine on top of Pawel's series, so you can
preempt parts of my rebase using
b4 am -P 1,2,4-6,8,9,11-15,17-20 cover.1794347059.git.u.kleine-koenig@baylibre.com
Just give me a poke when you made up your mind how to proceed and sorry
for missing that conflict.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-11-11 9:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 21:54 [PATCH v4 00/20] mfd: Use named initializers for arrays of *_device_data Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 01/20] mfd: bcm2835-pm: Remove member of struct bcm2835_pm that is only used locally Uwe Kleine-König (The Capable Hub)
2026-11-11 9:30 ` Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 02/20] mfd: bcm2835-pm: Drop unused header Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 03/20] mfd: kempld: Simplify device abstraction Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 04/20] mfd: lp87565: Explicitly set driver data for the generic dt compatible Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 05/20] mfd: mt6360: Drop irrelevant __maybe_unused Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 06/20] mfd: rt4831: " Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 07/20] mfd: loongson-se: Drop unused assignment of acpi_device_id driver data Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 08/20] mfd: Drop unused assignment of i2c_device_id " Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 09/20] mfd: Drop unused assignment of platform_device_id " Uwe Kleine-König (The Capable Hub)
2026-11-10 23:05 ` Benson Leung
2026-11-10 21:54 ` [PATCH v4 10/20] mfd: Use named initializers for acpi_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-11-11 8:45 ` Andy Shevchenko
2026-11-11 9:55 ` Uwe Kleine-König (The Capable Hub) [this message]
2026-11-10 21:54 ` [PATCH v4 11/20] mfd: intel-m10-bmc-pmci: Use named initializers for dfl_device_id array Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 12/20] mfd: Use named initializers for arrays of i2c_device_id Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 13/20] mfd: twl6030: Use named initializers for of_device_id Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 14/20] mfd: Use PCI_DEVICE* macros to initialize pci_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 15/20] mfd: Use named initializers for platform_device_id array Uwe Kleine-König (The Capable Hub)
2026-11-10 23:07 ` Benson Leung
2026-11-10 21:54 ` [PATCH v4 16/20] mfd: Unify style of acpi_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 17/20] mfd: Unify style of dmi_system_id arrays Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 18/20] mfd: Unify style of i2c_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-11-10 21:54 ` [PATCH v4 19/20] mfd: Unify style of of_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-11-11 2:15 ` Chen-Yu Tsai
2026-11-11 5:54 ` Luca Ceresoli
2026-11-11 6:30 ` Matti Vaittinen
2026-11-10 21:54 ` [PATCH v4 20/20] mfd: Unify style of pci_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=avQ19KBnQ2mnhZa-@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=david.rhodes@cirrus.com \
--cc=lee@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--cc=mika.westerberg@linux.intel.com \
--cc=patches@opensource.cirrus.com \
--cc=pzalewski@thegoodpenguin.co.uk \
--cc=qipeng.zha@intel.com \
--cc=rf@opensource.cirrus.com \
--cc=thomas.richard@bootlin.com \
--cc=zhaoqunqin@loongson.cn \
/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
all inboxes | Powered by JetHome®