From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: |WARNING| pw158669 [PATCH v2 1/1] eal: correct memory ordering in MCS lock
Date: Tue, 11 Nov 2025 18:38:44 +0100 (CET) [thread overview]
Message-ID: <20251111173844.27F6E1261F1@dpdk.org> (raw)
In-Reply-To: <20251111173850.790254-1-wathsala.vithanage@arm.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/158669
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#108: FILE: lib/eal/include/rte_mcslock.h:68:
+ * Must synchronize with R2 the releasing CAS in unlock(), this will ensure
^^^
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#195: FILE: lib/eal/include/rte_mcslock.h:140:
+ * A3: Another thread was enqueued concurrently, so the CAS and the lock
^^^
total: 0 errors, 2 warnings, 140 lines checked
next prev parent reply other threads:[~2025-11-11 17:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251111173850.790254-1-wathsala.vithanage@arm.com>
2025-11-11 17:14 ` |SUCCESS| " qemudev
2025-11-11 17:19 ` qemudev
2025-11-11 17:38 ` checkpatch [this message]
2025-11-11 18:27 ` 0-day Robot
2025-11-11 18:27 ` 0-day Robot
2025-11-11 18:43 ` |PENDING| pw158669 [PATCH] [v2,1/1] eal: correct memory ordering in dpdklab
2025-11-11 18:44 ` |SUCCESS| " dpdklab
2025-11-11 18:45 ` dpdklab
2025-11-11 19:04 ` |PENDING| " dpdklab
2025-11-11 19:08 ` |SUCCESS| " dpdklab
2025-11-11 19:15 ` |PENDING| " dpdklab
2025-11-11 19:17 ` dpdklab
2025-11-11 19:17 ` dpdklab
2025-11-11 19:53 ` |SUCCESS| " dpdklab
2025-11-11 20:01 ` dpdklab
2025-11-11 20:14 ` dpdklab
2025-11-11 20:14 ` dpdklab
2025-11-11 20:15 ` dpdklab
2025-11-11 20:42 ` 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=20251111173844.27F6E1261F1@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=wathsala.vithanage@arm.com \
/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).