> > It seems, however, that this slipped through the cracks. My Debian > > kernelconfig has I2C_COMPAT still enabled, so I am reluctant to remove > > it from one kernel release to the next. > > > One reason may be that the default for I2C_COMPAT is still y. > We should switch this to n, even though it doesn't help in cases like > make oldconfig. Yes, but we should still do it. > > I wonder if we need some printout that it is really going away for a few > > kernel releases. > > > This may be a compromise. > However I wonder how likely it is that somebody uses the latest kernel > and hasn't updated his userspace tools for > 15 yrs. I am not worrying about using old versions of lmsensors, this is super unlikely. I worry about custom applications using the deprecated path. Like, IPMI docs advertised this path up to now (I fixed it). And why should one change that path if the kernel is not complaining?
Attachment:
signature.asc
Description: PGP signature
