Hello, On Fri, Jul 17, 2026 at 12:31:20PM +0200, Uwe Kleine-König (The Capable Hub) wrote: > On Wed, Jun 10, 2026 at 07:10:51PM +0200, Uwe Kleine-König (The Capable Hub) wrote: > > On Mon, May 18, 2026 at 12:41:43PM +0200, Uwe Kleine-König (The Capable Hub) wrote: > > > Hello, > > > > > > I plan to do the following to the definition of i2c_device_id: > > > > > > diff --git a/include/linux/mod_devicetable.h b/include/linux/mod_devicetable.h > > > index 23ff24080dfd..aebd3a5e90af 100644 > > > --- a/include/linux/mod_devicetable.h > > > +++ b/include/linux/mod_devicetable.h > > > @@ -477,7 +477,11 @@ struct rpmsg_device_id { > > > > > > struct i2c_device_id { > > > char name[I2C_NAME_SIZE]; > > > - kernel_ulong_t driver_data; /* Data private to the driver */ > > > + union { > > > + /* Data private to the driver */ > > > + kernel_ulong_t driver_data; > > > + const void *driver_data_ptr; > > > + }; > > > }; > > > > > > /* pci_epf */ > > > > I want to work on that, but I'd need this patch series to be in for it. > > Do you still have this patch on your radar? > > While I still have to make several patches land before I can modify > struct i2c_device_id, getting the patches from this thread in would at > least make my queue smaller. > > FTR: The series still applies fine to next-20260716. It's November and the series still applies to next-20261116. Does someone still have this patch set on their radar? Best regards Uwe