Re: [net-next 0/8][pull request] 1GbE Intel Wired LAN Driver Updates 2018-01-24

From: Alexander Duyck Date: Wed, 24 Jan 2018 18:29:42 -0800 > I'll double check our VF drivers and make sure none of them are > exposing a netdevice with an all 0's MAC address, and see what we can > do about relocating the locally administered address generation into

Re: [net-next 0/8][pull request] 1GbE Intel Wired LAN Driver Updates 2018-01-24

On Wed, Jan 24, 2018 at 1:10 PM, David Miller wrote: > From: Jeff Kirsher > Date: Wed, 24 Jan 2018 12:55:12 -0800 > >> This series contains updates to igb and e1000e only. > > Pulled, however: > >> Corinna Vinschen implements the ability to set

Re: [net-next 0/8][pull request] 1GbE Intel Wired LAN Driver Updates 2018-01-24

From: Jeff Kirsher Date: Wed, 24 Jan 2018 12:55:12 -0800 > This series contains updates to igb and e1000e only. Pulled, however: > Corinna Vinschen implements the ability to set the VF MAC to > 00:00:00:00:00:00 via RTM_SETLINK on the PF, to prevent receiving >

[net-next 0/8][pull request] 1GbE Intel Wired LAN Driver Updates 2018-01-24

This series contains updates to igb and e1000e only. Corinna Vinschen implements the ability to set the VF MAC to 00:00:00:00:00:00 via RTM_SETLINK on the PF, to prevent receiving "invlaid argument" when libvirt attempts to restore the MAC address back to its original state of 00:00:00:00:00:00.