[ovs-dev] [PATCH 0/8] Linux upstream kernel backports and updates

Justin Pettit jpettit at ovn.org
Fri Feb 16 09:44:00 UTC 2018



> On Feb 16, 2018, at 12:52 AM, Pravin Shelar <pshelar at ovn.org> wrote:
> 
> On Wed, Feb 14, 2018 at 3:18 PM, Greg Rose <gvrose8192 at 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?

--Justin




More information about the dev mailing list