From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: |WARNING| pw156623 [PATCH 1/1] ring: safe partial ordering for head/tail update
Date: Mon, 15 Sep 2025 20:54:57 +0200 (CEST) [thread overview]
Message-ID: <20250915185457.2C58D12406A@dpdk.org> (raw)
In-Reply-To: <20250915185451.533039-2-wathsala.vithanage@arm.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/156623
_coding style issues_
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#81:
loads, and CAS operations. However, this approach introduces a
^^^
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#86:
the CAS and the preceding load of the head by converting them to
^^^
total: 0 errors, 2 warnings, 22 lines checked
next prev parent reply other threads:[~2025-09-15 18:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250915185451.533039-2-wathsala.vithanage@arm.com>
2025-09-15 18:21 ` |SUCCESS| " qemudev
2025-09-15 18:26 ` qemudev
2025-09-15 18:54 ` checkpatch [this message]
2025-09-15 19:21 ` |PENDING| pw156623 [PATCH] [1/1] ring: safe partial ordering for hea dpdklab
2025-09-15 19:21 ` dpdklab
2025-09-15 19:28 ` |SUCCESS| " dpdklab
2025-09-15 19:43 ` |PENDING| " dpdklab
2025-09-15 19:45 ` |SUCCESS| " dpdklab
2025-09-15 19:45 ` dpdklab
2025-09-15 19:47 ` |PENDING| " dpdklab
2025-09-15 19:48 ` |SUCCESS| " dpdklab
2025-09-15 19:58 ` |SUCCESS| pw156623 [PATCH 1/1] ring: safe partial ordering for head/tail update 0-day Robot
2025-09-15 19:58 ` 0-day Robot
2025-09-15 19:59 ` |SUCCESS| pw156623 [PATCH] [1/1] ring: safe partial ordering for hea dpdklab
2025-09-15 20:01 ` dpdklab
2025-09-15 20:02 ` dpdklab
2025-09-15 20:03 ` dpdklab
2025-09-15 20:05 ` dpdklab
2025-09-15 21:45 ` 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=20250915185457.2C58D12406A@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).