From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Congjie Zhou <zcjie0802@qq.com>
Subject: |WARNING| pw148474 [PATCH] eal/linux: redefine the name for rte_fbarray_init
Date: Thu, 14 Nov 2024 09:12:19 +0100 (CET) [thread overview]
Message-ID: <20241114081219.BA648121E2B@dpdk.org> (raw)
In-Reply-To: <tencent_B2075C50A573ADACC57248F416668EE42C09@qq.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/148474
_coding style issues_
ERROR:TRAILING_WHITESPACE: trailing whitespace
#97: FILE: lib/eal/linux/eal_memalloc.c:1434:
+static uint64_t $
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#97: FILE: lib/eal/linux/eal_memalloc.c:1434:
+static uint64_t
+current_time(void) {
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#99: FILE: lib/eal/linux/eal_memalloc.c:1436:
+ struct timespec ts;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#100: FILE: lib/eal/linux/eal_memalloc.c:1437:
+ if (clock_gettime(CLOCK_MONOTONIC_RAW, &ts) == -1) {$
ERROR:CODE_INDENT: code indent should use tabs where possible
#101: FILE: lib/eal/linux/eal_memalloc.c:1438:
+ EAL_LOG(ERR, "Fail to get current time");$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#101: FILE: lib/eal/linux/eal_memalloc.c:1438:
+ EAL_LOG(ERR, "Fail to get current time");$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#103: FILE: lib/eal/linux/eal_memalloc.c:1440:
+ }$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#104: FILE: lib/eal/linux/eal_memalloc.c:1441:
+ uint64_t time_ns = (uint64_t)ts.tv_sec * 1000000000ULL + ts.tv_nsec;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#105: FILE: lib/eal/linux/eal_memalloc.c:1442:
+ return time_ns;$
total: 3 errors, 6 warnings, 34 lines checked
next prev parent reply other threads:[~2024-11-14 8:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_B2075C50A573ADACC57248F416668EE42C09@qq.com>
2024-11-14 7:39 ` |SUCCESS| pw148474 [PATCH] eal/linux: redefine the name for rte_fbarray_init() qemudev
2024-11-14 7:43 ` qemudev
2024-11-14 8:12 ` checkpatch [this message]
2024-11-14 10:23 ` |SUCCESS| pw148474 [PATCH] eal/linux: redefine the name for rte_fbar dpdklab
2024-11-14 10:50 ` dpdklab
2024-11-14 10:50 ` dpdklab
2024-11-14 11:05 ` dpdklab
2024-11-14 11:40 ` dpdklab
2024-11-14 12:14 ` dpdklab
2024-11-14 15:47 ` dpdklab
2024-11-14 15:51 ` |PENDING| " dpdklab
2024-11-14 16:46 ` dpdklab
2024-11-14 16:56 ` |SUCCESS| " dpdklab
2024-11-14 17:24 ` |PENDING| " dpdklab
2024-11-14 17:41 ` |SUCCESS| " dpdklab
2024-11-14 18:21 ` |WARNING| " dpdklab
2024-11-14 19:58 ` |SUCCESS| " dpdklab
2024-11-14 20:31 ` dpdklab
2024-11-14 20:48 ` |WARNING| " dpdklab
2024-11-14 22:11 ` |SUCCESS| " dpdklab
2024-11-14 22:20 ` dpdklab
2024-11-14 22: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=20241114081219.BA648121E2B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=zcjie0802@qq.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).