-
- Downloads
PCI: remove dynids.use_driver_data
The driver flag dynids.use_driver_data is almost consistently not set, and causes more problems than it solves. It was initially intended as a flag to indicate whether a driver's usage of driver_data had been carefully inspected and was ready for values from userspace. That audit was never done, so most drivers just get a 0 for driver_data when new IDs are added from userspace via sysfs. So remove the flag, allowing drivers to see the data directly (a followon patch validates the passed driver_data value against what the drivers expect). Acked-by:Greg Kroah-Hartman <gregkh@suse.de> Acked-by:
Jean Delvare <khali@linux-fr.org> Signed-off-by:
Milton Miller <miltonm@bga.com> Signed-off-by:
Jesse Barnes <jbarnes@virtuousgeek.org>
Showing
- drivers/i2c/busses/i2c-amd756.c 0 additions, 1 deletiondrivers/i2c/busses/i2c-amd756.c
- drivers/i2c/busses/i2c-viapro.c 0 additions, 1 deletiondrivers/i2c/busses/i2c-viapro.c
- drivers/pci/pci-driver.c 1 addition, 2 deletionsdrivers/pci/pci-driver.c
- drivers/scsi/ipr.c 0 additions, 1 deletiondrivers/scsi/ipr.c
- include/linux/pci.h 0 additions, 1 deletioninclude/linux/pci.h
Loading
Please register or sign in to comment