Bleep bloop. Greetings Tonghao Zhang, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: Line is 86 characters long (recommended limit is 79)
#451 FILE: lib/tnl-neigh-cache.c:600:
VLOG_ERR("Can't create nln handle or notifier for neighboring
subsystem");
WARNING: Line is 83 characters long (recommended limit is 79)
#517 FILE: vswitchd/vswitch.xml:228:
Set this value to <code>true</code> to enable learning neigh from
system.
WARNING: Line is 84 characters long (recommended limit is 79)
#521 FILE: vswitchd/vswitch.xml:232:
If enabled, Open vSwitch can learn the neigh entries from system.
Then you
WARNING: Line is 85 characters long (recommended limit is 79)
#523 FILE: vswitchd/vswitch.xml:234:
when encapsulating tunnel packets(e.g. native_tunnel_output), we try
to use
WARNING: Line is 92 characters long (recommended limit is 79)
#524 FILE: vswitchd/vswitch.xml:235:
the neigh entry which learned from system. That is useful for the
flow bifurcation
WARNING: Line is 83 characters long (recommended limit is 79)
#526 FILE: vswitchd/vswitch.xml:237:
to split traffic between Linux user space and kernel space. More
details:
WARNING: Line is 91 characters long (recommended limit is 79)
#527 FILE: vswitchd/vswitch.xml:238:
http://git.dpdk.org/next/dpdk-next-net/tree/doc/guides/howto/flow_bifurcation.rst
Lines checked: 536, Warnings: 7, Errors: 0
Please check this out. If you feel there has been an error, please email
[email protected]
Thanks,
0-day Robot
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
