diff options
| author | Bjørn Mork <bjorn@mork.no> | 2018-05-02 22:22:54 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-05-26 08:48:47 +0200 |
| commit | 10bffef7fb2614f17319198146feee1769270f1e (patch) | |
| tree | 749b0589ffa0c89aee3c443feadf0ca92fe43205 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 02ce46ba5c009d926c7a07fb9f79d39d7aa89fbc (diff) | |
qmi_wwan: do not steal interfaces from class drivers
[ Upstream commit 5697db4a696c41601a1d15c1922150b4dbf5726c ]
The USB_DEVICE_INTERFACE_NUMBER matching macro assumes that
the { vendorid, productid, interfacenumber } set uniquely
identifies one specific function. This has proven to fail
for some configurable devices. One example is the Quectel
EM06/EP06 where the same interface number can be either
QMI or MBIM, without the device ID changing either.
Fix by requiring the vendor-specific class for interface number
based matching. Functions of other classes can and should use
class based matching instead.
Fixes: 03304bcb5ec4 ("net: qmi_wwan: use fixed interface number matching")
Signed-off-by: Bjørn Mork <bjorn@mork.no>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions
