Good point, I will add a following patch to do this.

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

On 6 February 2017 at 16:46, Yang, Yi Y <yi.y.y...@intel.com> wrote:
> Joe, I checked current ovs and net-next kernel, obviously some patches from 
> net-next are selectively backported to ovs, but others are not, I'm not sure 
> what the policy is for a new patch. It will be better that the person who did 
> the patch backports it to ovs at the same time, but nobody did so.

That's supposed to be the policy; However, depending on the patch sometimes 
openvswitch isn't even the main target of the change, so the contributor may 
not be aware they should do so. There may be added difficulty if the previous 
contributor didn't do their backport. I think that lately there hasn't been 
particularly close co-ordination between the trees, but ideally I think that as 
we approach an OVS release, we would try to sync them up.

> My 802.1ad backport has included all the things l3 patch set depends 
> on, so I think you can give it a go :-)

Kicking off a build on my local tester, I can at least report back on that. I 
see you've tested on a few platforms as well, that's great. If you were able to 
add even one or two basic tests to the system-kmod-testsuite for the new L3 
bits (eg, set up a tunnel and send some packets through it), that would sure go 
some way towards knowing that this series does what it intends without bad 
side-effects, and also would help us to catch any potential regressions.

> To make sure 802.1ad to work, there is still a userspace work to do, but as 
> Pravin said, this has no business with l3 patch set.

Sure thing, userspace can be decoupled.
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to