From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Cheng Jiang <cheng1.jiang@intel.com>
Subject: |WARNING| pw126907 [PATCH v3] app/dma-perf: introduce dma-perf application
Date: Wed, 17 May 2023 10:08:27 +0200 (CEST) [thread overview]
Message-ID: <20230517080827.B2C2D120565@dpdk.org> (raw)
In-Reply-To: <20230517073108.43627-1-cheng1.jiang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/126907
_coding style issues_
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#132: FILE: app/test-dma-perf/benchmark.c:6:
+#include <stdio.h>
WARNING:LONG_LINE: line length of 118 exceeds 100 columns
#217: FILE: app/test-dma-perf/benchmark.c:91:
+ printf("average cycles/op: %" PRIu64 ", buffer size: %u, nr_buf: %u, memory: %uMB, frequency: %" PRIu64 ".
",
WARNING:LONG_LINE: line length of 106 exceeds 100 columns
#269: FILE: app/test-dma-perf/benchmark.c:143:
+ rte_exit(EXIT_FAILURE, "Error, no configured queues reported on device id. %u
", dev_id);
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#673: FILE: app/test-dma-perf/main.c:5:
+#include <stdio.h>
WARNING:LONG_LINE: line length of 103 exceeds 100 columns
#742: FILE: app/test-dma-perf/main.c:74:
+ snprintf(output_str[1], MAX_OUTPUT_STR_LEN, "CPU frequency,%" PRIu64 "
", rte_get_timer_hz());
WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#985: FILE: app/test-dma-perf/main.c:317:
+ printf("Error: No case type in case %d, the test will be finished here.
", i + 1);
total: 0 errors, 6 warnings, 1190 lines checked
next prev parent reply other threads:[~2023-05-17 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230517073108.43627-1-cheng1.jiang@intel.com>
2023-05-17 7:56 ` |SUCCESS| " qemudev
2023-05-17 8:00 ` qemudev
2023-05-17 8:08 ` checkpatch [this message]
2023-05-17 9:00 ` 0-day Robot
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=20230517080827.B2C2D120565@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=cheng1.jiang@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).