[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <99053387-16ff-9ed0-ef12-7bcbc7a7af2e@intel.com>
Date: Wed, 5 Apr 2023 18:50:55 -0600
From: Ahmed Zaki <ahmed.zaki@...el.com>
To: Jakub Kicinski <kuba@...nel.org>,
Tony Nguyen <anthony.l.nguyen@...el.com>
CC: <davem@...emloft.net>, <pabeni@...hat.com>, <edumazet@...gle.com>,
<netdev@...r.kernel.org>,
Rafal Romanowski <rafal.romanowski@...el.com>
Subject: Re: [PATCH net 1/2] iavf: refactor VLAN filter states
On 2023-04-05 18:15, Jakub Kicinski wrote:
> On Tue, 4 Apr 2023 10:25:21 -0700 Tony Nguyen wrote:
>> + __IAVF_VLAN_INVALID,
>> + __IAVF_VLAN_ADD, /* filter needs to be added */
>> + __IAVF_VLAN_IS_NEW, /* filter is new, wait for PF answer */
>> + __IAVF_VLAN_ACTIVE, /* filter is accepted by PF */
>> + __IAVF_VLAN_REMOVE, /* filter needs to be removed */
> Why the leading underscores?
Just following the convention. iavf_tc_state_t and
iavf_cloud_filter_state_t have these underscores. Same for iavf_state_t.
Powered by blists - more mailing lists