From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: |WARNING| pw133336 [PATCH v3 18/19] timer: use rte optional stdatomic API
Date: Thu, 26 Oct 2023 02:36:13 +0200 (CEST) [thread overview]
Message-ID: <20231026003613.47DF8120A1D@dpdk.org> (raw)
In-Reply-To: <1698280314-25861-19-git-send-email-roretzla@linux.microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/133336
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#105: FILE: lib/timer/rte_timer.c:213:
+ rte_atomic_store_explicit(&tim->status.u32, status.u32, rte_memory_order_relaxed);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#114: FILE: lib/timer/rte_timer.c:234:
+ prev_status.u32 = rte_atomic_load_explicit(&tim->status.u32, rte_memory_order_relaxed);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#127: FILE: lib/timer/rte_timer.c:257:
+ success = rte_atomic_compare_exchange_strong_explicit(&tim->status.u32,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#140: FILE: lib/timer/rte_timer.c:280:
+ prev_status.u32 = rte_atomic_load_explicit(&tim->status.u32, rte_memory_order_relaxed);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#153: FILE: lib/timer/rte_timer.c:296:
+ success = rte_atomic_compare_exchange_strong_explicit(&tim->status.u32,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#166: FILE: lib/timer/rte_timer.c:533:
+ rte_atomic_store_explicit(&tim->status.u32, status.u32, rte_memory_order_release);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#175: FILE: lib/timer/rte_timer.c:615:
+ rte_atomic_store_explicit(&tim->status.u32, status.u32, rte_memory_order_release);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#185: FILE: lib/timer/rte_timer.c:649:
+ return rte_atomic_load_explicit(&tim->status.state,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#196: FILE: lib/timer/rte_timer.c:756:
+ rte_atomic_store_explicit(&tim->status.u32, status.u32,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#207: FILE: lib/timer/rte_timer.c:769:
+ rte_atomic_store_explicit(&tim->status.u32, status.u32,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#218: FILE: lib/timer/rte_timer.c:944:
+ rte_atomic_store_explicit(&tim->status.u32, status.u32,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#229: FILE: lib/timer/rte_timer.c:957:
+ rte_atomic_store_explicit(&tim->status.u32, status.u32,
total: 0 errors, 12 warnings, 135 lines checked
parent reply other threads:[~2023-10-26 0:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1698280314-25861-19-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=20231026003613.47DF8120A1D@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).