From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@huawei.com>
Subject: |WARNING| pw158630 [PATCH v3 1/1] ring: fix unsafe ordering for head/tail update
Date: Mon, 10 Nov 2025 11:17:38 +0100 (CET) [thread overview]
Message-ID: <20251110101738.1EAF91261F1@dpdk.org> (raw)
In-Reply-To: <20251110101717.233685-2-konstantin.ananyev@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/158630
_coding style issues_
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#90:
loads, and CAS operations. However, this approach introduces a
^^^
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#95:
the CAS and the preceding load of the head by converting them to
^^^
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#168: 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'?
#190: 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, 4 warnings, 59 lines checked
next prev parent reply other threads:[~2025-11-10 10:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251110101717.233685-2-konstantin.ananyev@huawei.com>
2025-11-10 9:43 ` |SUCCESS| " qemudev
2025-11-10 9:48 ` qemudev
2025-11-10 10:17 ` checkpatch [this message]
2025-11-10 10:53 ` |SUCCESS| pw158630 [PATCH] [v3,1/1] ring: fix unsafe ordering for he dpdklab
2025-11-10 10:54 ` |PENDING| " dpdklab
2025-11-10 10:58 ` |SUCCESS| " dpdklab
2025-11-10 11:05 ` |PENDING| " dpdklab
2025-11-10 11:11 ` |SUCCESS| " dpdklab
2025-11-10 11:13 ` dpdklab
2025-11-10 11:15 ` dpdklab
2025-11-10 11:20 ` |PENDING| " dpdklab
2025-11-10 11:27 ` dpdklab
2025-11-10 11:29 ` dpdklab
2025-11-10 11:34 ` |SUCCESS| " dpdklab
2025-11-10 11:39 ` dpdklab
2025-11-10 11:46 ` dpdklab
2025-11-10 11:46 ` |SUCCESS| pw158630 [PATCH v3 1/1] ring: fix unsafe ordering for head/tail update 0-day Robot
2025-11-10 11:46 ` 0-day Robot
2025-11-10 12:08 ` |SUCCESS| pw158630 [PATCH] [v3,1/1] ring: fix unsafe ordering for he dpdklab
2025-11-10 12:42 ` dpdklab
2025-11-10 13:01 ` dpdklab
2025-11-10 16:26 ` dpdklab
2025-11-10 16:56 ` dpdklab
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=20251110101738.1EAF91261F1@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).