[ovs-dev] [PATCH 5/8] datapath: Add support for kernel 4.4

Jesse Gross jesse at kernel.org
Mon Jul 18 21:48:18 UTC 2016


On Mon, Jul 18, 2016 at 11:43 PM, pravin shelar <pshelar at ovn.org> wrote:
> On Mon, Jul 18, 2016 at 11:28 AM, Jesse Gross <jesse at kernel.org> wrote:
>> On Mon, Jul 18, 2016 at 4:24 AM, Pravin B Shelar <pshelar at ovn.org> wrote:
>> /home/jgross/openvswitch/datapath/linux/vxlan.c:1905:45: warning:
>> incorrect type in assignment (different base types)
>> /home/jgross/openvswitch/datapath/linux/vxlan.c:1905:45:    expected
>> restricted __be16 [usertype] dst_port
>> /home/jgross/openvswitch/datapath/linux/vxlan.c:1905:45:    got int
>> /home/jgross/openvswitch/datapath/linux/vxlan.c:1933:58: warning:
>> incorrect type in argument 7 (different base types)
>> /home/jgross/openvswitch/datapath/linux/vxlan.c:1933:58:    expected
>> unsigned int [unsigned] [usertype] vni
>> /home/jgross/openvswitch/datapath/linux/vxlan.c:1933:58:    got
>> restricted __be32 [usertype] remote_vni
>>
> This is upstream issue, I will have to send patch upstream to fix it.
> anyways OVS is not affected by this, so I will keep it as it is for
> now.

It looks like the first one is an upstream issue and can wait (but is
already fixed in net-next). But I think the second one in
vxlan_fdb_create() is a difference between OVS backports and upstream.



More information about the dev mailing list