From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: |WARNING| pw142738 [PATCH v4 4/4] eal: describe Arm CPU features including WFXT
Date: Fri, 26 Jul 2024 19:17:04 +0200 (CEST) [thread overview]
Message-ID: <20240726171704.1A7C3127C81@dpdk.org> (raw)
In-Reply-To: <20240726171528.2245682-4-wathsala.vithanage@arm.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/142738
_coding style issues_
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#94: FILE: lib/eal/arm/include/rte_cpuflags_64.h:41:
+ * LDADD, LDCLR, LDEOR, LDSET, LDSMAX, LDSMIN, LDUMAX, LDUMIN, CAS,
total: 0 errors, 1 warnings, 76 lines checked
next prev parent reply other threads:[~2024-07-26 17:17 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240726171528.2245682-4-wathsala.vithanage@arm.com>
2024-07-26 16:56 ` |SUCCESS| pw142739-142738 " qemudev
2024-07-26 17:00 ` qemudev
2024-07-26 17:17 ` checkpatch [this message]
2024-07-26 18:03 ` |SUCCESS| pw142738 " 0-day Robot
2024-07-26 21:23 ` |PENDING| pw142739-142738 [PATCH] [v4,4/4] eal: describe Arm CPU fea dpdklab
2024-07-26 21:24 ` |SUCCESS| " dpdklab
2024-07-26 21:25 ` dpdklab
2024-07-26 21:26 ` dpdklab
2024-07-26 21:27 ` dpdklab
2024-07-26 21:30 ` dpdklab
2024-07-26 21:30 ` dpdklab
2024-07-26 21:31 ` dpdklab
2024-07-26 21:32 ` |PENDING| " dpdklab
2024-07-26 21:33 ` |SUCCESS| " dpdklab
2024-07-26 21:35 ` dpdklab
2024-07-26 21:39 ` dpdklab
2024-07-26 21:40 ` dpdklab
2024-07-26 21:40 ` |PENDING| " dpdklab
2024-07-26 21:44 ` |SUCCESS| " dpdklab
2024-07-26 21:45 ` dpdklab
2024-07-26 21:47 ` dpdklab
2024-07-26 21:52 ` |PENDING| " dpdklab
2024-07-26 21:55 ` dpdklab
2024-07-26 21:58 ` dpdklab
2024-07-26 21:58 ` dpdklab
2024-07-26 21:59 ` dpdklab
2024-07-26 21:59 ` |SUCCESS| " dpdklab
2024-07-26 22:00 ` |PENDING| " dpdklab
2024-07-26 22:01 ` dpdklab
2024-07-26 22:03 ` dpdklab
2024-07-26 22:04 ` dpdklab
2024-07-26 22:04 ` dpdklab
2024-07-26 22:05 ` dpdklab
2024-07-26 22:06 ` |SUCCESS| " dpdklab
2024-07-26 22:06 ` |PENDING| " dpdklab
2024-07-26 22:07 ` dpdklab
2024-07-26 22:08 ` dpdklab
2024-07-26 22:09 ` dpdklab
2024-07-26 22:14 ` dpdklab
2024-07-26 22:14 ` dpdklab
2024-07-26 22:14 ` dpdklab
2024-07-26 22:17 ` dpdklab
2024-07-26 22:17 ` dpdklab
2024-07-26 22:18 ` dpdklab
2024-07-26 22:19 ` dpdklab
2024-07-26 22:20 ` dpdklab
2024-07-26 22:20 ` dpdklab
2024-07-26 22:20 ` dpdklab
2024-07-26 22:21 ` dpdklab
2024-07-26 22:22 ` dpdklab
2024-07-26 22:22 ` dpdklab
2024-07-26 22:22 ` dpdklab
2024-07-26 22:23 ` dpdklab
2024-07-26 22:23 ` dpdklab
2024-07-26 22:23 ` dpdklab
2024-07-26 22:25 ` dpdklab
2024-07-26 22:27 ` dpdklab
2024-07-26 22:28 ` |SUCCESS| " dpdklab
2024-07-26 22:29 ` dpdklab
2024-07-26 22:29 ` |PENDING| " dpdklab
2024-07-26 22:29 ` dpdklab
2024-07-26 22:29 ` dpdklab
2024-07-26 22:31 ` dpdklab
2024-07-26 22:33 ` dpdklab
2024-07-26 22:36 ` dpdklab
2024-07-26 22:38 ` dpdklab
2024-07-26 22:40 ` dpdklab
2024-07-26 22:43 ` dpdklab
2024-07-26 22:44 ` dpdklab
2024-07-26 22:44 ` dpdklab
2024-07-26 22:47 ` dpdklab
2024-07-26 22:49 ` dpdklab
2024-07-26 22:49 ` dpdklab
2024-07-26 22:50 ` dpdklab
2024-07-26 22:52 ` dpdklab
2024-07-26 22:52 ` dpdklab
2024-07-26 22:52 ` dpdklab
2024-07-26 22:53 ` dpdklab
2024-07-26 22:53 ` dpdklab
2024-07-26 22:54 ` dpdklab
2024-07-26 22:55 ` dpdklab
2024-07-26 22:55 ` dpdklab
2024-07-26 22:56 ` dpdklab
2024-07-26 22:56 ` dpdklab
2024-07-26 22:57 ` dpdklab
2024-07-26 22:58 ` dpdklab
2024-07-26 22:59 ` dpdklab
2024-07-26 23:00 ` dpdklab
2024-07-26 23:00 ` dpdklab
2024-07-26 23:01 ` dpdklab
2024-07-26 23:02 ` dpdklab
2024-07-26 23:03 ` dpdklab
2024-07-26 23:03 ` dpdklab
2024-07-26 23:04 ` dpdklab
2024-07-26 23:05 ` dpdklab
2024-07-26 23:05 ` dpdklab
2024-07-26 23:08 ` dpdklab
2024-07-26 23:09 ` dpdklab
2024-07-26 23:10 ` |SUCCESS| " dpdklab
2024-07-26 23:13 ` |PENDING| " dpdklab
2024-07-27 0:40 ` |SUCCESS| " 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=20240726171704.1A7C3127C81@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).