summaryrefslogtreecommitdiffstats
path: root/drivers/net/bonding/bond_main.c
diff options
context:
space:
mode:
authorBjørn Mork2012-07-17 13:14:32 +0200
committerDavid S. Miller2012-07-18 18:31:25 +0200
commit1817e83d6ccf992164dd83522b2d1c22b1a85977 (patch)
tree3fbea43d4ea36ecdd61aec298d393e829e33f596 /drivers/net/bonding/bond_main.c
parentb44: add 64 bit stats (diff)
downloadkernel-qcow2-linux-1817e83d6ccf992164dd83522b2d1c22b1a85977.tar.gz
kernel-qcow2-linux-1817e83d6ccf992164dd83522b2d1c22b1a85977.tar.xz
kernel-qcow2-linux-1817e83d6ccf992164dd83522b2d1c22b1a85977.zip
net: qmi_wwan: make dynamic device IDs work
The usbnet API use the device ID table to store a pointer to a minidriver. Setting a generic pointer for dynamic device IDs will in most cases make them work as expected. usbnet will otherwise treat the dynamic IDs as blacklisted. That is rarely useful. There is no standard class describing devices supported by this driver, and most vendors don't even provide enough information to allow vendor specific wildcard matching. The result is that most of the supported devices must be explicitly listed in the device table. Allowing dynamic IDs to work both simplifies testing and verification of new devices, and provides a way for end users to use a device before the ID is added to the driver. Signed-off-by: Bjørn Mork <bjorn@mork.no> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/bonding/bond_main.c')
0 files changed, 0 insertions, 0 deletions