On Thu, Nov 28, 2024 at 04:42:09PM +0100, Hans de Goede wrote: > Not all devices have an ACPI companion fwnode, so adev might be NULL. This > can e.g. (theoretically) happen when a user manually binds one of > the int3472 drivers to another i2c/platform device through sysfs. > > Add a check for adev not being set and return -ENODEV in that case. But what kind of "bad thing" can happen in such cases? If none, why this change? -- With Best Regards, Andy Shevchenko
