automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: |WARNING| pw158672 [PATCH v4 3/3] ring: establish a safe partial order in rts-ring
Date: Tue, 11 Nov 2025 19:17:18 +0100 (CET)	[thread overview]
Message-ID: <20251111181718.72D7C1261F1@dpdk.org> (raw)
In-Reply-To: <20251111181639.830527-3-wathsala.vithanage@arm.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/158672

_coding style issues_


WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#51: 
Enforce a safe partial order by making the CAS and the preceding head
                                           ^^^

WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#81: FILE: lib/ring/rte_ring_rts_elem_pvt.h:35:
+	 * A0 = {A0.a, A0.b}: Synchronizes with the CAS at R0.
 	                                            ^^^

WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#82: FILE: lib/ring/rte_ring_rts_elem_pvt.h:36:
+	 * The CAS at R0 in same typed thread establishes a happens-before
 	       ^^^

WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#88: FILE: lib/ring/rte_ring_rts_elem_pvt.h:42:
+	 * holds when CAS succeeds and A0.b when it fails.
 	              ^^^

WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#155: FILE: lib/ring/rte_ring_rts_elem_pvt.h:128:
+		 * A1 Synchronizes with the CAS at R1.
 		                            ^^^

total: 0 errors, 5 warnings, 120 lines checked

      parent reply	other threads:[~2025-11-11 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251111181639.830527-3-wathsala.vithanage@arm.com>
2025-11-11 17:51 ` |SUCCESS| pw158670-158672 " qemudev
2025-11-11 17:56 ` qemudev
2025-11-11 18:17 ` checkpatch [this message]

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=20251111181718.72D7C1261F1@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).