On Thu, 26 Feb 2026 21:21:35 +0100, Wolfram Sang <[email protected]> said: > On Mon, Feb 23, 2026 at 09:59:29AM +0100, Bartosz Golaszewski wrote: >> It's been another year of discussing the object life-time problems at >> conferences. I2C is one of the offenders and its problems are more >> complex than those of some other subsystems. It seems the revocable[1] >> API may make its way into the kernel this year but even with it in >> place, I2C won't be able to use it as there's currently nothing to >> *revoke*. The struct device is embedded within the i2c_adapter struct >> whose lifetime is tied to the provider device being bound to its driver. >> >> Fixing this won't be fast and easy but nothing's going to happen if we >> don't start chipping away at it. The ultimate goal in order to be able >> to use an SRCU-based solution (revocable or otherwise) is to convert the >> embedded struct device in struct i2c_adapter into an __rcu pointer that >> can be *revoked*. To that end we need to hide all dereferences of >> adap->dev in drivers. >> >> This series addresses the usage of adap->dev in device printk() helpers >> (dev_err() et al). It introduces a set of i2c-specific helpers and >> starts using them across bus drivers. For now just 12 patches but I'll >> keep on doing it if these get accepted. Once these get upstream for >> v6.20/7.0, we'll be able to also start converting i2c drivers outside of >> drivers/i2c/. > > I applied the series to for-current but squashed the user conversions > into patch 1. Changes are trivial enough and I don't want the pull > request to look excessive, so it can go in smoothly. Hope you are fine > with it. >
Sure, do you still want me to send these changes in separate patches for review? Bart
