Re: [PATCH net-next] Name NICs based on vmbus offer and enable async probe by default

2019-07-25 Thread David Miller
1) Subject: line lacks proper subsystem prefix 2) No module parameters in networking drivers, sorry. Find some generic way to do this via devlink or similar.

RE: [PATCH net-next] Name NICs based on vmbus offer and enable async probe by default

2019-07-09 Thread Haiyang Zhang
Srinivasan ; Stephen > Hemminger ; o...@aepfle.de; vkuznets > ; linux-kernel@vger.kernel.org > Subject: Re: [PATCH net-next] Name NICs based on vmbus offer and enable > async probe by default > > > The net-next tree, if you are reading netdev today, has been closed. I will re-submit when the tree re-opened. Thanks, - Haiyang

RE: [PATCH net-next] Name NICs based on vmbus offer and enable async probe by default

2019-07-09 Thread Haiyang Zhang
...@davemloft.net; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH net-next] Name NICs based on vmbus offer and enable > async probe by default > > On Tue, 9 Jul 2019 22:56:30 + > Haiyang Zhang wrote: > > > - VRSS_CHANNEL_MAX);

Re: [PATCH net-next] Name NICs based on vmbus offer and enable async probe by default

2019-07-09 Thread David Miller
The net-next tree, if you are reading netdev today, has been closed.

Re: [PATCH net-next] Name NICs based on vmbus offer and enable async probe by default

2019-07-09 Thread Stephen Hemminger
On Tue, 9 Jul 2019 22:56:30 + Haiyang Zhang wrote: > - VRSS_CHANNEL_MAX); > + if (probe_type == PROBE_PREFER_ASYNCHRONOUS) { > + snprintf(name, IFNAMSIZ, "eth%d", dev->channel->dev_num); What about PCI passthrough or VF devices that are also being