From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: |WARNING| pw133330 [PATCH v3 09/19] rcu: use rte optional stdatomic API
Date: Thu, 26 Oct 2023 02:34:07 +0200 (CEST) [thread overview]
Message-ID: <20231026003408.01844120A1D@dpdk.org> (raw)
In-Reply-To: <1698280314-25861-10-git-send-email-roretzla@linux.microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/133330
_coding style issues_
WARNING:TYPO_SPELLING: 'THRID' may be misspelled - perhaps 'THIRD'?
#105: FILE: lib/rcu/rte_rcu_qsbr.c:105:
+ old_bmap = rte_atomic_load_explicit(__RTE_QSBR_THRID_ARRAY_ELM(v, i),
WARNING:TYPO_SPELLING: 'THRID' may be misspelled - perhaps 'THIRD'?
#134: FILE: lib/rcu/rte_rcu_qsbr.c:157:
+ old_bmap = rte_atomic_load_explicit(__RTE_QSBR_THRID_ARRAY_ELM(v, i),
WARNING:TYPO_SPELLING: 'THRID' may be misspelled - perhaps 'THIRD'?
#165: FILE: lib/rcu/rte_rcu_qsbr.c:230:
+ bmap = rte_atomic_load_explicit(__RTE_QSBR_THRID_ARRAY_ELM(v, i),
WARNING:TYPO_SPELLING: 'THRID' may be misspelled - perhaps 'THIRD'?
#185: FILE: lib/rcu/rte_rcu_qsbr.c:251:
+ bmap = rte_atomic_load_explicit(__RTE_QSBR_THRID_ARRAY_ELM(v, i),
WARNING:TYPO_SPELLING: 'THRID' may be misspelled - perhaps 'THIRD'?
#214: FILE: lib/rcu/rte_rcu_qsbr.h:66:
+#define __RTE_QSBR_THRID_ARRAY_ELM_SIZE (sizeof(RTE_ATOMIC(uint64_t)) * 8)
WARNING:TYPO_SPELLING: 'THRID' may be misspelled - perhaps 'THIRD'?
#219: FILE: lib/rcu/rte_rcu_qsbr.h:70:
+#define __RTE_QSBR_THRID_ARRAY_ELM(v, i) ((uint64_t __rte_atomic *) \
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#354: FILE: lib/rcu/rte_rcu_qsbr.h:520:
+ RTE_ATOMIC(uint64_t) *reg_thread_id;
^
total: 1 errors, 6 warnings, 296 lines checked
parent reply other threads:[~2023-10-26 0:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1698280314-25861-10-git-send-email-roretzla@linux.microsoft.com>]
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=20231026003408.01844120A1D@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=roretzla@linux.microsoft.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).