Re: [PATCH net-next v3] cdc_ether: Improve ZTE MF823/831/910 handling

2016-07-22 Thread kbuild test robot
Hi, [auto build test WARNING on net-next/master] url: https://github.com/0day-ci/linux/commits/Kristian-Evensen/cdc_ether-Improve-ZTE-MF823-831-910-handling/20160723-093100 config: x86_64-randconfig-i0-201629 (attached as .config) compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3 reproduce:

Re: [PATCH net-next v3] cdc_ether: Improve ZTE MF823/831/910 handling

2016-07-20 Thread David Miller
From: Kristian Evensen Date: Tue, 19 Jul 2016 16:54:11 +0200 > The firmware in several ZTE devices (at least the MF823/831/910 > modems/mifis) use OS fingerprinting to determine which type of device to > export. In addition, these devices export a REST API which can

Re: [PATCH net-next v3] cdc_ether: Improve ZTE MF823/831/910 handling

2016-07-20 Thread Oliver Neukum
On Tue, 2016-07-19 at 16:54 +0200, Kristian Evensen wrote: > The firmware in several ZTE devices (at least the MF823/831/910 > modems/mifis) use OS fingerprinting to determine which type of device > to > export. In addition, these devices export a REST API which can be used > to > control the type

[PATCH net-next v3] cdc_ether: Improve ZTE MF823/831/910 handling

2016-07-19 Thread Kristian Evensen
The firmware in several ZTE devices (at least the MF823/831/910 modems/mifis) use OS fingerprinting to determine which type of device to export. In addition, these devices export a REST API which can be used to control the type of device. So far, on Linux, the devices have been seen as RNDIS or