From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: |WARNING| pw140311 [PATCH] event/dsw: support explicit release only mode
Date: Fri, 24 May 2024 21:35:16 +0200 (CEST) [thread overview]
Message-ID: <20240524193516.A785212367B@dpdk.org> (raw)
In-Reply-To: <20240524192437.183960-1-mattias.ronnblom@ericsson.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/140311
_coding style issues_
WARNING:TYPO_SPELLING: 'RELASE' may be misspelled - perhaps 'RELEASE'?
#153:
events of type RTE_EVENT_OP_FORWARD and RTE_EVENT_OP_RELASE) that has
WARNING:TYPO_SPELLING: 'efficency' may be misspelled - perhaps 'efficiency'?
#156:
For efficency reasons, DSW does not track the *identity* of individual
WARNING:TYPO_SPELLING: 'relase' may be misspelled - perhaps 'release'?
#172:
latency is reduced, regardless if implicit relase is enabled or not.
total: 0 errors, 3 warnings, 224 lines checked
next prev parent reply other threads:[~2024-05-24 19:35 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240524192437.183960-1-mattias.ronnblom@ericsson.com>
2024-05-24 19:08 ` |SUCCESS| " qemudev
2024-05-24 19:12 ` qemudev
2024-05-24 19:35 ` checkpatch [this message]
2024-05-24 20:23 ` |FAILURE| " 0-day Robot
2024-05-25 15:20 ` |SUCCESS| pw140311 [PATCH] event/dsw: support explicit release only dpdklab
2024-05-25 15:22 ` dpdklab
2024-05-25 15:22 ` dpdklab
2024-05-25 15:23 ` dpdklab
2024-05-25 15:23 ` dpdklab
2024-05-25 15:25 ` dpdklab
2024-05-25 15:28 ` dpdklab
2024-05-25 15:41 ` dpdklab
2024-05-25 15:42 ` dpdklab
2024-05-25 15:42 ` dpdklab
2024-05-25 15:43 ` dpdklab
2024-05-25 15:43 ` dpdklab
2024-05-25 15:43 ` dpdklab
2024-05-25 15:44 ` dpdklab
2024-05-25 15:44 ` dpdklab
2024-05-25 15:44 ` dpdklab
2024-05-25 15:44 ` dpdklab
2024-05-25 15:45 ` dpdklab
2024-05-25 15:45 ` dpdklab
2024-05-25 15:45 ` dpdklab
2024-05-25 15:45 ` dpdklab
2024-05-25 15:46 ` dpdklab
2024-05-25 15:50 ` dpdklab
2024-05-25 15:52 ` dpdklab
2024-05-25 15:52 ` dpdklab
2024-05-25 15:53 ` dpdklab
2024-05-25 15:54 ` dpdklab
2024-05-25 15:54 ` dpdklab
2024-05-25 15:54 ` dpdklab
2024-05-25 15:55 ` dpdklab
2024-05-25 15:55 ` dpdklab
2024-05-25 15:55 ` dpdklab
2024-05-25 15:55 ` dpdklab
2024-05-25 15:55 ` dpdklab
2024-05-25 15:56 ` dpdklab
2024-05-25 15:56 ` |FAILURE| " dpdklab
2024-05-25 15:57 ` |SUCCESS| " dpdklab
2024-05-25 15:57 ` dpdklab
2024-05-25 15:58 ` |FAILURE| " dpdklab
2024-05-25 15:58 ` |SUCCESS| " dpdklab
2024-05-25 15:59 ` |FAILURE| " dpdklab
2024-05-25 16:01 ` dpdklab
2024-05-25 16:02 ` dpdklab
2024-05-25 16:04 ` |SUCCESS| " dpdklab
2024-05-25 16:04 ` dpdklab
2024-05-25 16:07 ` |FAILURE| " dpdklab
2024-05-25 16:10 ` |SUCCESS| " dpdklab
2024-05-25 16:14 ` dpdklab
2024-05-25 16:16 ` dpdklab
2024-05-25 16:16 ` dpdklab
2024-05-25 16:18 ` dpdklab
2024-05-25 16:18 ` dpdklab
2024-05-25 16:18 ` dpdklab
2024-05-25 16:22 ` |FAILURE| " dpdklab
2024-05-25 16:23 ` |SUCCESS| " dpdklab
2024-05-25 16:23 ` dpdklab
2024-05-25 16:23 ` dpdklab
2024-05-25 16:24 ` dpdklab
2024-05-25 16:27 ` dpdklab
2024-05-25 16:30 ` dpdklab
2024-05-25 16:31 ` dpdklab
2024-05-25 16:31 ` dpdklab
2024-05-25 16:32 ` dpdklab
2024-05-25 16:32 ` dpdklab
2024-05-25 16:32 ` |FAILURE| " dpdklab
2024-05-25 16:33 ` |SUCCESS| " dpdklab
2024-05-25 16:34 ` dpdklab
2024-05-25 16:35 ` |FAILURE| " dpdklab
2024-05-25 16:37 ` |SUCCESS| " dpdklab
2024-05-25 16:37 ` |FAILURE| " dpdklab
2024-05-25 16:39 ` dpdklab
2024-05-25 16:42 ` |SUCCESS| " dpdklab
2024-05-25 16:42 ` dpdklab
2024-05-25 16:43 ` dpdklab
2024-05-25 16:46 ` dpdklab
2024-05-25 16:48 ` dpdklab
2024-05-25 16:48 ` dpdklab
2024-05-25 16:48 ` dpdklab
2024-05-25 16:48 ` dpdklab
2024-05-25 16:51 ` dpdklab
2024-05-25 16:52 ` dpdklab
2024-05-25 16:52 ` dpdklab
2024-05-25 16:55 ` dpdklab
2024-05-25 18:28 ` dpdklab
2024-05-25 18:34 ` dpdklab
2024-05-28 21:03 ` dpdklab
2024-05-28 21:39 ` 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=20240524193516.A785212367B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=mattias.ronnblom@ericsson.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).