Re: [PATCH v2 00/23] mfd: Use named initializers for arrays of *_device_data
Andy Shevchenko <[email protected]>
| Newsgroups | org.kernel.vger.linux-samsung-soc,dev.linux.lists.asahi,dev.linux.lists.chrome-platform,dev.linux.lists.imx,dev.linux.lists.linux-sunxi,dev.linux.lists.mfd,org.infradead.lists.linux-amlogic,org.infradead.lists.linux-mediatek,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-crypto,org.kernel.vger.linux-kernel,org.kernel.vger.linux-omap,org.kernel.vger.linux-renesas-soc,org.kernel.vger.linux-sound |
|---|---|
| Organization | Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo |
| Message-ID | <[email protected]> |
On Wed, Jul 08, 2026 at 01:15:07PM +0200, Uwe Kleine-König (The Capable Hub) wrote: > Hello, > > this series superseeds my previous patch "[PATCH v1] mfd: Use named > initializers for arrays of i2c_device_data" > (https://lore.kernel.org/lkml/[email protected]) > that Lee asked me to rebase and also the series "[PATCH v1 0/3] mfd: > Initialize spi_device_id arrays using member names" > (https://lore.kernel.org/lkml/[email protected]). > > The objective for this series is to prepare mfd for changing > of_device_id etc to make driver_data a union, see > https://lore.kernel.org/all/[email protected]/ > for the idea behind it. > > This series is based on yesterday's next/master and it does the > restructuring not only for i2c and spi (as the two series mentioned > above), but for all *_device_id structures that I intend to modify with > a union that affect mfd. So (I hope) this is the only patch series > affecting mfd for this quest. > > I don't care much about the last few patches unifying the coding style. > I think it's a good opportunity to do that, but if you don't like them, > just don't apply these. The patches bring inconsistency (or still leave it) with the terminator style in both I²C and ACPI ID tables. Can you revisit that? -- With Best Regards, Andy Shevchenko