From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Daniel Gregory <daniel.gregory@bytedance.com>
Subject: |WARNING| pw139803 [RFC PATCH] eal/riscv: add support for zawrs extension
Date: Fri, 3 May 2024 11:50:55 +0200 (CEST) [thread overview]
Message-ID: <20240503095055.57B37122141@dpdk.org> (raw)
In-Reply-To: <20240502144149.66446-1-daniel.gregory@bytedance.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/139803
_coding style issues_
WARNING:TYPO_SPELLING: 'nto' may be misspelled - perhaps 'not'?
#92:
* Call wrs.nto - this blocks until the reservation set is invalidated by
WARNING:TYPO_SPELLING: 'NTO' may be misspelled - perhaps 'NOT'?
#220: FILE: lib/eal/riscv/include/rte_pause.h:96:
+#define __RTE_RISCV_WRS_NTO() { asm volatile("wrs.nto" : : : "memory"); }
WARNING:TYPO_SPELLING: 'nto' may be misspelled - perhaps 'not'?
#220: FILE: lib/eal/riscv/include/rte_pause.h:96:
+#define __RTE_RISCV_WRS_NTO() { asm volatile("wrs.nto" : : : "memory"); }
WARNING:TYPO_SPELLING: 'NTO' may be misspelled - perhaps 'NOT'?
#234: FILE: lib/eal/riscv/include/rte_pause.h:110:
+ __RTE_RISCV_WRS_NTO();
WARNING:TYPO_SPELLING: 'NTO' may be misspelled - perhaps 'NOT'?
#251: FILE: lib/eal/riscv/include/rte_pause.h:127:
+ __RTE_RISCV_WRS_NTO();
WARNING:TYPO_SPELLING: 'NTO' may be misspelled - perhaps 'NOT'?
#268: FILE: lib/eal/riscv/include/rte_pause.h:144:
+ __RTE_RISCV_WRS_NTO();
WARNING:TYPO_SPELLING: 'NTO' may be misspelled - perhaps 'NOT'?
#283: FILE: lib/eal/riscv/include/rte_pause.h:159:
+ __RTE_RISCV_WRS_NTO(); \
total: 0 errors, 7 warnings, 162 lines checked
next prev parent reply other threads:[~2024-05-03 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240502144149.66446-1-daniel.gregory@bytedance.com>
2024-05-02 14:19 ` |SUCCESS| " qemudev
2024-05-02 14:24 ` qemudev
2024-05-02 15:44 ` 0-day Robot
2024-05-03 8:21 ` |WARNING| " checkpatch
2024-05-03 9:50 ` checkpatch [this message]
2024-05-03 9:57 ` checkpatch
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=20240503095055.57B37122141@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=daniel.gregory@bytedance.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).