On Fri, Feb 16, 2018 at 1:44 AM, Justin Pettit <jpet...@ovn.org> wrote:
>
>
>> On Feb 16, 2018, at 12:52 AM, Pravin Shelar <pshe...@ovn.org> wrote:
>>
>> On Wed, Feb 14, 2018 at 3:18 PM, Greg Rose <gvrose8...@gmail.com> wrote:
>>> Pull in the remaining available upstream bug fixes for the openvswitch
>>> Linux kernel datapath. In addition, allow building the openvswitch
>>> OOT kernel datapath on kernels up to and including Linux kernel release
>>> 4.15.
>>>
>>> Travis build is here - Note that the errors are not related to this
>>> patch series:
>>>
>>> https://travis-ci.org/gvrose8192/ovs-experimental/builds/341649151
>>>
>>> The patches can be pulled from here in case that is easier for review.
>>>
>>> https://github.com/gvrose8192/ovs-experimental/tree/linux-4.15
>>>
>>> The patches are based on commit in the master branch:
>>> f50c1eb4a6 ("docs: Update supported DPDK versions.")
>>>
>>> After this series the remaining upstream patches for openvswitch are
>>> all erspan related. The erspan patches will be sent separately at a
>>> later date.
>>>
>>> Christopher Díaz Riveros (1):
>>> datapath: Remove unneeded semicolons
>>>
>>> Ed Swierk (1):
>>> datapath: Remove padding from packet before L3+ conntrack processing
>>>
>>> Eric Garver (1):
>>> datapath: Fix pop_vlan action for double tagged frames
>>>
>>> Greg Rose (2):
>>> acinclude: Enable building for Linux kernel 4.15
>>> travis: Update Linux kernel test list
>>>
>>> Julia Lawall (1):
>>> datapath: drop unneeded newline
>>>
>>> Yang Shi (1):
>>> datapath: remove unused hardirq.h
>>>
>>> paolo abeni (1):
>>> datapath: do not propagate headroom updates to internal port
>>>
>> All patches looks good to me. I pushed all patches to master.
>>
>> I also backport following three patches to branch 2.8 and 2.9:-
>> datapath: do not propagate headroom updates to internal port
>> datapath: Fix pop_vlan action for double tagged frames
>> datapath: Remove padding from packet before L3+ conntrack processing
>
> Thanks, Pravin! Will support for building against Linux 4.15 apply cleanly
> to branch-2.9? Do you have any concerns about our doing that?
>
At this point 2.9 supports 4.13, so we will need to pull in patch
series for 4.14 and 4.15 to the branch 2.9.
OVS 2.9 missing datapath features like NSH and metering, available in
upstream kernel 4.14 and 4.15, is that ok?
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
