From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Christensen <drc@linux.ibm.com>
Subject: |WARNING| pw142297 [PATCH v6] eal: verify mmu type for DPDK support ppc64le
Date: Thu, 11 Jul 2024 01:22:02 +0200 (CEST) [thread overview]
Message-ID: <20240710232203.04C6A128144@dpdk.org> (raw)
In-Reply-To: <20240710232122.3581128-1-drc@linux.ibm.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/142297
_coding style issues_
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#296: FILE: lib/eal/ppc/rte_mmu.c:5:
+#include <stdio.h>
ERROR:CODE_INDENT: code indent should use tabs where possible
#395: FILE: lib/eal/windows/eal.c:299:
+ if (!eal_mmu_supported()) {$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#395: FILE: lib/eal/windows/eal.c:299:
+ if (!eal_mmu_supported()) {$
ERROR:CODE_INDENT: code indent should use tabs where possible
#396: FILE: lib/eal/windows/eal.c:300:
+ rte_eal_init_alert("Unsupported MMU type.");$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#396: FILE: lib/eal/windows/eal.c:300:
+ rte_eal_init_alert("Unsupported MMU type.");$
ERROR:CODE_INDENT: code indent should use tabs where possible
#397: FILE: lib/eal/windows/eal.c:301:
+ rte_errno = ENOTSUP;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#397: FILE: lib/eal/windows/eal.c:301:
+ rte_errno = ENOTSUP;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#398: FILE: lib/eal/windows/eal.c:302:
+ return -1;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#398: FILE: lib/eal/windows/eal.c:302:
+ return -1;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#399: FILE: lib/eal/windows/eal.c:303:
+ }$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#399: FILE: lib/eal/windows/eal.c:303:
+ }$
total: 5 errors, 6 warnings, 193 lines checked
next prev parent reply other threads:[~2024-07-10 23:22 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240710232122.3581128-1-drc@linux.ibm.com>
2024-07-10 22:56 ` |SUCCESS| pw142297 [PATCH v6] eal: verify mmu type for DPDK support (ppc64le) qemudev
2024-07-10 23:01 ` qemudev
2024-07-10 23:22 ` checkpatch [this message]
2024-07-11 0:23 ` 0-day Robot
2024-07-11 0:28 ` |SUCCESS| pw142297 [PATCH] [v6] eal: verify mmu type for DPDK suppor dpdklab
2024-07-11 0:32 ` dpdklab
2024-07-11 0:32 ` |PENDING| " dpdklab
2024-07-11 0:34 ` dpdklab
2024-07-11 0:35 ` |SUCCESS| " dpdklab
2024-07-11 0:36 ` dpdklab
2024-07-11 0:45 ` dpdklab
2024-07-11 0:49 ` dpdklab
2024-07-11 0:51 ` |PENDING| " dpdklab
2024-07-11 0:52 ` |SUCCESS| " dpdklab
2024-07-11 0:52 ` |PENDING| " dpdklab
2024-07-11 0:57 ` dpdklab
2024-07-11 0:57 ` dpdklab
2024-07-11 0:59 ` dpdklab
2024-07-11 1:01 ` dpdklab
2024-07-11 1:05 ` dpdklab
2024-07-11 1:07 ` dpdklab
2024-07-11 1:07 ` dpdklab
2024-07-11 1:08 ` |SUCCESS| " dpdklab
2024-07-11 1:09 ` dpdklab
2024-07-11 1:14 ` |PENDING| " dpdklab
2024-07-11 1:16 ` dpdklab
2024-07-11 1:16 ` dpdklab
2024-07-11 1:18 ` dpdklab
2024-07-11 1:20 ` dpdklab
2024-07-11 1:25 ` dpdklab
2024-07-11 1:25 ` |SUCCESS| " dpdklab
2024-07-11 1:30 ` dpdklab
2024-07-11 1:44 ` |PENDING| " dpdklab
2024-07-11 1:45 ` |SUCCESS| " dpdklab
2024-07-11 1:45 ` |PENDING| " dpdklab
2024-07-11 1:48 ` dpdklab
2024-07-11 1:50 ` dpdklab
2024-07-11 1:50 ` dpdklab
2024-07-11 1:58 ` dpdklab
2024-07-11 1:59 ` dpdklab
2024-07-11 2:02 ` dpdklab
2024-07-11 2:04 ` dpdklab
2024-07-11 2:08 ` dpdklab
2024-07-11 2:11 ` dpdklab
2024-07-11 2:12 ` dpdklab
2024-07-11 2:18 ` dpdklab
2024-07-11 2:20 ` dpdklab
2024-07-11 2:23 ` dpdklab
2024-07-11 2:28 ` dpdklab
2024-07-11 2:29 ` dpdklab
2024-07-11 2:31 ` dpdklab
2024-07-11 2:31 ` dpdklab
2024-07-11 2:32 ` dpdklab
2024-07-11 2:34 ` dpdklab
2024-07-11 2:35 ` dpdklab
2024-07-11 2:37 ` dpdklab
2024-07-11 2:37 ` dpdklab
2024-07-11 2:38 ` dpdklab
2024-07-11 2:42 ` dpdklab
2024-07-11 2:42 ` dpdklab
2024-07-11 2:45 ` dpdklab
2024-07-11 2:50 ` dpdklab
2024-07-11 2:50 ` dpdklab
2024-07-11 2:52 ` dpdklab
2024-07-11 2:53 ` dpdklab
2024-07-11 2:54 ` dpdklab
2024-07-11 2:56 ` dpdklab
2024-07-11 2:56 ` dpdklab
2024-07-11 2:56 ` dpdklab
2024-07-11 2:57 ` dpdklab
2024-07-11 2:58 ` dpdklab
2024-07-11 2:58 ` dpdklab
2024-07-11 2:59 ` dpdklab
2024-07-11 3:00 ` dpdklab
2024-07-11 3:00 ` dpdklab
2024-07-11 3:01 ` dpdklab
2024-07-11 3:02 ` dpdklab
2024-07-11 3:03 ` dpdklab
2024-07-11 3:04 ` dpdklab
2024-07-11 3:04 ` dpdklab
2024-07-11 3:07 ` dpdklab
2024-07-11 3:11 ` |SUCCESS| " dpdklab
2024-07-11 3:12 ` dpdklab
2024-07-11 3:12 ` |PENDING| " dpdklab
2024-07-11 3:13 ` dpdklab
2024-07-11 3:15 ` dpdklab
2024-07-11 3:16 ` dpdklab
2024-07-11 3:16 ` dpdklab
2024-07-11 3:17 ` dpdklab
2024-07-11 3:17 ` dpdklab
2024-07-11 3:17 ` |SUCCESS| " dpdklab
2024-07-11 3:21 ` |PENDING| " dpdklab
2024-07-11 3:22 ` dpdklab
2024-07-11 3:24 ` dpdklab
2024-07-11 3:27 ` dpdklab
2024-07-11 3:29 ` dpdklab
2024-07-11 3:29 ` dpdklab
2024-07-11 3:30 ` dpdklab
2024-07-11 3:30 ` dpdklab
2024-07-11 3:31 ` dpdklab
2024-07-11 3:35 ` dpdklab
2024-07-11 3:38 ` dpdklab
2024-07-11 3:42 ` dpdklab
2024-07-11 3:44 ` dpdklab
2024-07-11 3:46 ` dpdklab
2024-07-11 3:48 ` |SUCCESS| " dpdklab
2024-07-11 3:48 ` |PENDING| " dpdklab
2024-07-11 3:49 ` |SUCCESS| " dpdklab
2024-07-11 3:50 ` dpdklab
2024-07-11 3:51 ` dpdklab
2024-07-11 3:52 ` dpdklab
2024-07-13 5:59 ` dpdklab
2024-07-14 7:35 ` dpdklab
2024-07-14 13:57 ` dpdklab
2024-07-14 23:25 ` dpdklab
2024-07-14 23:38 ` 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=20240710232203.04C6A128144@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=drc@linux.ibm.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).