i2c: Legacy i2c drivers shouldn't issue uevents
authorDavid Brownell <david-b@pacbell.net>
Tue, 22 May 2007 17:49:16 +0000 (19:49 +0200)
committerJean Delvare <khali@hyperion.delvare>
Tue, 22 May 2007 17:49:16 +0000 (19:49 +0200)
commitde81d2aaebc8e5e5167cb93f674c57705898e45e
treed452f6b0f41879617a75e1fe9092f196de108bf1
parentd25790532370e7448e3d3bd25a17e1e9f1299816
i2c: Legacy i2c drivers shouldn't issue uevents

Prevent legacy drivers from issuing uevents for device creation/removal,
so that userspace can't cause modprobing loops for them.  This became a
problem for some legacy PC drivers.  I can't easily see it becoming an
issue with I2C legacy drivers, but consistency-in-paranoia seems likely
to be a good thing here.  For usable i2c-level driver model uevents, just
switch to a new-style driver.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Jean Delvare <khali@linux-fr.org>
drivers/i2c/i2c-core.c