automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Doug Foster <doug.foster@arm.com>
Subject: |WARNING| pw143765 [PATCH] rcu: refactor rcu register/unregister functions
Date: Fri,  6 Sep 2024 22:53:14 +0200 (CEST)	[thread overview]
Message-ID: <20240906205314.1CE38121D10@dpdk.org> (raw)
In-Reply-To: <20240906205219.629266-1-doug.foster@arm.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'THRID' may be misspelled - perhaps 'THIRD'?
#102: FILE: lib/rcu/rte_rcu_qsbr.c:101:
+	old_bmap = rte_atomic_fetch_or_explicit(__RTE_QSBR_THRID_ARRAY_ELM(v, i),

WARNING:TYPO_SPELLING: 'THRID' may be misspelled - perhaps 'THIRD'?
#155: FILE: lib/rcu/rte_rcu_qsbr.c:139:
+	old_bmap = rte_atomic_fetch_and_explicit(__RTE_QSBR_THRID_ARRAY_ELM(v, i),

total: 0 errors, 2 warnings, 111 lines checked

  parent reply	other threads:[~2024-09-06 20:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240906205219.629266-1-doug.foster@arm.com>
2024-09-06 20:27 ` |SUCCESS| " qemudev
2024-09-06 20:32 ` qemudev
2024-09-06 20:53 ` checkpatch [this message]
2024-09-06 21:44 ` 0-day Robot
2024-09-10  2:43 ` |SUCCESS| pw143765 [PATCH] rcu: refactor rcu register/unregister fun dpdklab
2024-09-10  2:43 ` dpdklab
2024-09-10  3:21 ` dpdklab
2024-09-10  6:43 ` |PENDING| " dpdklab
2024-09-10  6:57 ` dpdklab
2024-09-10  7:07 ` dpdklab
2024-09-10  7:45 ` dpdklab
2024-09-10  9:30 ` |SUCCESS| " dpdklab
2024-09-10  9:45 ` dpdklab
2024-09-10  9:47 ` dpdklab
2024-09-10 10:02 ` dpdklab
2024-09-10 10:18 ` dpdklab
2024-09-10 13:15 ` dpdklab
2024-09-10 13:19 ` dpdklab
2024-09-10 13:23 ` dpdklab
2024-09-10 13:27 ` dpdklab
2024-09-10 13:46 ` dpdklab
2024-09-16  5:01 ` dpdklab
2024-09-16 11:37 ` 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=20240906205314.1CE38121D10@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=doug.foster@arm.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).