Friday, June 23, 2017 10:34 AM, Hemant Agrawal:
> On 6/21/2017 9:58 PM, Stephen Hemminger wrote:
> > Looking at some other issues, I noticed that both the TAP and MLX5
> > device drivers are looking at kernel version through uname. Although
> > this may seem like a good way to deal with kernel API
On Fri, 23 Jun 2017 13:03:55 +0530
Hemant Agrawal wrote:
> On 6/21/2017 9:58 PM, Stephen Hemminger wrote:
> > Looking at some other issues, I noticed that both the TAP and MLX5 device
> > drivers are looking at kernel version through uname. Although this may
> > seem like a good way to deal with
On 6/21/2017 9:58 PM, Stephen Hemminger wrote:
Looking at some other issues, I noticed that both the TAP and MLX5 device
drivers are looking at kernel version through uname. Although this may
seem like a good way to deal with kernel API changes, it is not reliable.
Enterprise kernel distro vend
Looking at some other issues, I noticed that both the TAP and MLX5 device
drivers are looking at kernel version through uname. Although this may
seem like a good way to deal with kernel API changes, it is not reliable.
Enterprise kernel distro vendors never change kernel version but do backport
f
4 matches
Mail list logo
