From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Hernan Vargas <hernan.vargas@intel.com>
Subject: |WARNING| pw141589 [PATCH v2 9/9] test/bbdev: remove unnecessary line
Date: Mon, 24 Jun 2024 17:08:40 +0200 (CEST) [thread overview]
Message-ID: <20240624150840.844B4128144@dpdk.org> (raw)
In-Reply-To: <20240624150237.47169-10-hernan.vargas@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/141589
_coding style issues_
WARNING:TYPO_SPELLING: 'unnecesary' may be misspelled - perhaps 'unnecessary'?
#69:
Remove unnecesary line of code.
total: 0 errors, 1 warnings, 7 lines checked
next prev parent reply other threads:[~2024-06-24 15:08 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240624150237.47169-10-hernan.vargas@intel.com>
2024-06-24 14:41 ` |SUCCESS| pw141582-141589 " qemudev
2024-06-24 14:46 ` qemudev
2024-06-24 15:08 ` checkpatch [this message]
2024-06-24 16:04 ` |SUCCESS| pw141589 " 0-day Robot
2024-06-25 0:19 ` |SUCCESS| pw141582-141589 [PATCH] [v2,9/9] test/bbdev: remove unnece dpdklab
2024-06-25 0:21 ` dpdklab
2024-06-25 0:24 ` dpdklab
2024-06-25 0:25 ` dpdklab
2024-06-25 0:30 ` dpdklab
2024-06-25 0:31 ` dpdklab
2024-06-25 0:33 ` dpdklab
2024-06-25 0:33 ` dpdklab
2024-06-25 0:36 ` dpdklab
2024-06-25 0:38 ` dpdklab
2024-06-25 0:40 ` dpdklab
2024-06-25 0:41 ` dpdklab
2024-06-25 1:01 ` dpdklab
2024-06-25 1:03 ` dpdklab
2024-06-25 1:19 ` dpdklab
2024-06-25 1:30 ` dpdklab
2024-06-25 1:56 ` dpdklab
2024-06-25 2:16 ` dpdklab
2024-06-25 2:17 ` dpdklab
2024-06-25 2:17 ` dpdklab
2024-06-25 2:19 ` dpdklab
2024-06-25 2:19 ` dpdklab
2024-06-25 2:20 ` dpdklab
2024-06-25 2:20 ` dpdklab
2024-06-25 2:20 ` dpdklab
2024-06-25 2:21 ` dpdklab
2024-06-25 2:26 ` dpdklab
2024-06-25 2:28 ` dpdklab
2024-06-25 2:29 ` dpdklab
2024-06-25 2:31 ` dpdklab
2024-06-25 2:44 ` dpdklab
2024-06-25 2:46 ` dpdklab
2024-06-25 2:47 ` dpdklab
2024-06-25 2:48 ` dpdklab
2024-06-25 3:16 ` dpdklab
2024-06-25 3:29 ` dpdklab
2024-06-25 3:37 ` dpdklab
2024-06-25 3:38 ` dpdklab
2024-06-25 3:39 ` dpdklab
2024-06-25 3:40 ` dpdklab
2024-06-25 3:41 ` dpdklab
2024-06-25 3:42 ` dpdklab
2024-06-25 3:43 ` dpdklab
2024-06-25 3:44 ` dpdklab
2024-06-25 3:45 ` dpdklab
2024-06-25 3:46 ` dpdklab
2024-06-25 3:46 ` dpdklab
2024-06-25 3:46 ` dpdklab
2024-06-25 3:46 ` dpdklab
2024-06-25 3:48 ` dpdklab
2024-06-25 3:54 ` dpdklab
2024-06-25 3:55 ` dpdklab
2024-06-25 3:55 ` dpdklab
2024-06-25 3:55 ` dpdklab
2024-06-25 4:11 ` dpdklab
2024-06-25 4:14 ` dpdklab
2024-06-25 4:14 ` dpdklab
2024-06-25 4:15 ` dpdklab
2024-06-25 4:15 ` dpdklab
2024-06-25 4:15 ` dpdklab
2024-06-25 4:16 ` dpdklab
2024-06-25 4:16 ` dpdklab
2024-06-25 4:16 ` dpdklab
2024-06-25 4:17 ` dpdklab
2024-06-25 4:19 ` dpdklab
2024-06-25 4:19 ` dpdklab
2024-06-25 4:20 ` dpdklab
2024-06-25 4:20 ` dpdklab
2024-06-25 4:22 ` dpdklab
2024-06-25 4:22 ` dpdklab
2024-06-25 4:23 ` dpdklab
2024-06-25 4:26 ` dpdklab
2024-06-25 4:26 ` dpdklab
2024-06-25 4:27 ` dpdklab
2024-06-25 4:27 ` dpdklab
2024-06-25 4:28 ` dpdklab
2024-06-25 4:28 ` dpdklab
2024-06-25 4:28 ` dpdklab
2024-06-25 4:29 ` dpdklab
2024-06-25 4:30 ` dpdklab
2024-06-25 4:31 ` dpdklab
2024-06-25 4:31 ` dpdklab
2024-06-25 4:44 ` dpdklab
2024-06-25 5:03 ` dpdklab
2024-06-25 5:03 ` dpdklab
2024-06-25 5:03 ` dpdklab
2024-06-25 5:04 ` dpdklab
2024-06-25 5:05 ` dpdklab
2024-06-25 5:06 ` dpdklab
2024-06-25 5:06 ` dpdklab
2024-06-25 5:10 ` dpdklab
2024-06-25 5:11 ` dpdklab
2024-06-25 5:15 ` dpdklab
2024-06-25 5:20 ` dpdklab
2024-06-25 5:22 ` dpdklab
2024-06-25 5:31 ` dpdklab
2024-06-25 5:32 ` dpdklab
2024-06-25 5:33 ` dpdklab
2024-06-25 5:35 ` dpdklab
2024-06-25 5:36 ` dpdklab
2024-06-25 5:37 ` dpdklab
2024-06-25 6:05 ` dpdklab
2024-06-25 6:10 ` dpdklab
2024-06-25 6:16 ` dpdklab
2024-06-25 6:19 ` dpdklab
2024-06-25 6:59 ` dpdklab
2024-06-25 7:34 ` dpdklab
2024-06-25 8:14 ` dpdklab
2024-06-25 8:20 ` dpdklab
2024-06-25 8:48 ` dpdklab
2024-06-25 9:16 ` dpdklab
2024-06-25 16:52 ` 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=20240624150840.844B4128144@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=hernan.vargas@intel.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).