[ovs-dev] [PATCH ovs-dev, dpdk-latest 1/2] ovs-atomic: Rename memory_order -> ovs_memory_order

0-day Robot robot at bytheb.org
Mon Oct 12 15:01:09 UTC 2020


Bleep bloop.  Greetings Eli Britstein, 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 80 characters long (recommended limit is 79)
#60 FILE: lib/ovs-atomic-flag-gcc4.7+.h:43:
atomic_flag_clear_explicit(volatile atomic_flag *object, ovs_memory_order order)

WARNING: Line is 82 characters long (recommended limit is 79)
#313 FILE: lib/ovs-atomic.h:109:
 * enum ovs_memory_order specifies the strictness of a memory barrier.  It has the

WARNING: Line is 83 characters long (recommended limit is 79)
#322 FILE: lib/ovs-atomic.h:186:
 * OVS atomics require the ovs_memory_order to be passed as a compile-time constant

WARNING: Line is 83 characters long (recommended limit is 79)
#446 FILE: lib/ovs-rcu.h:250:
static inline int ovsrcu_index_get__(const ovsrcu_index *i, ovs_memory_order order)

Lines checked: 461, Warnings: 4, Errors: 0


Please check this out.  If you feel there has been an error, please email aconole at redhat.com

Thanks,
0-day Robot


More information about the dev mailing list