[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180124.180236.687538947909157455.davem@davemloft.net>
Date: Wed, 24 Jan 2018 18:02:36 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: jeffrey.t.kirsher@...el.com
Cc: netdev@...r.kernel.org, nhorman@...hat.com, sassmann@...hat.com,
jogreene@...hat.com
Subject: Re: [net-next 0/7][pull request] 100GbE Intel Wired LAN Driver
Updates 2018-01-24
From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Date: Wed, 24 Jan 2018 14:45:39 -0800
> This series contains updates to fm10k only.
>
> Alex fixes MACVLAN offload for fm10k, where we were not seeing unicast
> packets being received because we did not correctly configure the
> default VLAN ID for the port and defaulting to 0.
>
> Jake cleans up unnecessary parenthesis in a couple of "if" statements.
> Fixed the driver to stop adding VLAN 0 into the VLAN table, since it
> would cause the VLAN table to be inconsistent between the PF and VF.
> Also fixed an issue where we were assuming that VLAN 1 is enabled when
> the default VLAN ID is not set, so resolve by not requesting any filters
> for the default_vid if it has not yet been assigned.
>
> Ngai fixes an issue which was generating a dmesg regarding unbale to
> kill a particular VLAN ID for the device. This is due to
> ndo_vlan_rx_kill_vid() exits with an error and the handler for this ndo
> is fm10k_update_vid() which exits prematurely under PF VLAN management.
> So to resolve, we must check the VLAN update action type before exiting
> fm10k_update_vid(), and act appropriately based on the action type.
> Also corrected code comment typos.
Looks good, pulled, thanks Jeff.
Powered by blists - more mailing lists