Re: [dpdk-dev] [RFC 00/14] link status API improvement and bugfixes

2018-01-05 Thread Stephen Hemminger
On Fri, 05 Jan 2018 15:29:09 +0100 Thomas Monjalon wrote: > 14/07/2017 20:30, Stephen Hemminger: > > While writing new driver, I noticed a lot of unnecessary duplication of > > code in drivers for handling the eth_dev link status information. While > > consolidating this, it also became obvious t

Re: [dpdk-dev] [RFC 00/14] link status API improvement and bugfixes

2018-01-05 Thread Thomas Monjalon
14/07/2017 20:30, Stephen Hemminger: > While writing new driver, I noticed a lot of unnecessary duplication of > code in drivers for handling the eth_dev link status information. While > consolidating this, it also became obvious that several drivers have > bugs in this are because they don't retur

Re: [dpdk-dev] [RFC 00/14] link status API improvement and bugfixes

2017-07-16 Thread Andrew Rybchenko
On 07/14/2017 09:30 PM, Stephen Hemminger wrote: While writing new driver, I noticed a lot of unnecessary duplication of code in drivers for handling the eth_dev link status information. While consolidating this, it also became obvious that several drivers have bugs in this are because they don't

[dpdk-dev] [RFC 00/14] link status API improvement and bugfixes

2017-07-14 Thread Stephen Hemminger
While writing new driver, I noticed a lot of unnecessary duplication of code in drivers for handling the eth_dev link status information. While consolidating this, it also became obvious that several drivers have bugs in this are because they don't return the correct value. Also, some drivers were