From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@huawei.com>
Subject: |WARNING| pw153564 [PATCH v1 3/4] ring: fix potential sync issue between head and tail values
Date: Wed, 21 May 2025 13:15:45 +0200 (CEST) [thread overview]
Message-ID: <20250521111545.6E749123FAA@dpdk.org> (raw)
In-Reply-To: <20250521111432.207936-4-konstantin.ananyev@huawei.com>
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
parent reply other threads:[~2025-05-21 11:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250521111432.207936-4-konstantin.ananyev@huawei.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250521111545.6E749123FAA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=test-report@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).