[ovs-dev] [PATCH v3 00/16] port Jiri Benc's L3 patchset to ovs

[Yang, Yi Y]

Then, are you merging https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328492.html or do I need to do anything else for it?

-----Original Message-----
From: Joe Stringer [mailto:joe at ovn.org] 
Sent: Thursday, February 9, 2017 9:44 AM
To: Yang, Yi Y <yi.y.yang at intel.com>
Cc: ovs dev <dev at openvswitch.org>; Yi-Hung Wei <yihung.wei at gmail.com>
Subject: Re: [ovs-dev] [PATCH v3 00/16] port Jiri Benc's L3 patchset to ovs

On 7 February 2017 at 21:15, Yang, Yi Y <yi.y.yang at intel.com> wrote:
> Joe, I investigated all the patches which changed 
> include/linux/if_vlan.h for 802.1ad in net-next again, I found ovs 
> compat mode doesn't need most of them at all, 
> datapath/linux/compat/include/linux/ only includes part of changes 
> which aren't in local  $KSRC/include/linux/ but required in 
> datapath/linux/compat/*.c

^ required in datapath/linux/compat/*.c, or datapath/*.c. If a function doesn't exist in an older kernel, a backport is needed - whether in the headers or datapath/linux/compat/*.c. Also, if the behaviour of one of those functions changes on a newer kernel which requires changes to the users (such as datapath/*.c), then they may also need updating.

> , so my conclusion is we needn't them at all, https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328492.html is enough for 802.1ad backport for ovs.

At a glance I think you're right.