* |WARNING| pw153564 [PATCH v1 3/4] ring: fix potential sync issue between head and tail values
[not found] <20250521111432.207936-4-konstantin.ananyev@huawei.com>
@ 2025-05-21 11:15 ` checkpatch
0 siblings, 0 replies; only message in thread
From: checkpatch @ 2025-05-21 11:15 UTC (permalink / raw)
To: test-report; +Cc: Konstantin Ananyev
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153564
_coding style issues_
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#61:
"ring/soring: fix synchronization issue between head and tail values"
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#67:
It uses Acquire-Release memory ordering for CAS operation in move_head().
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#118: FILE: lib/ring/rte_ring_c11_pvt.h:89:
+ * d->head load, but before CAS operation for the d->head.
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#133: FILE: lib/ring/rte_ring_c11_pvt.h:116:
+ * this CAS(ACQ_REL, ACQUIRE) serves as a hoist
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#158: FILE: lib/ring/rte_ring_hts_elem_pvt.h:119:
+ * this CAS(ACQ_REL, ACQUIRE) serves as a hoist barrier to prevent:
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#180: FILE: lib/ring/rte_ring_rts_elem_pvt.h:134:
+ * this CAS(ACQ_REL, ACQUIRE) serves as a hoist barrier to prevent:
total: 0 errors, 6 warnings, 99 lines checked
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-05-21 11:16 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20250521111432.207936-4-konstantin.ananyev@huawei.com>
2025-05-21 11:15 ` |WARNING| pw153564 [PATCH v1 3/4] ring: fix potential sync issue between head and tail values checkpatch
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).