From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Christensen <drc@linux.ibm.com>
Subject: |WARNING| pw155501 [PATCH] trace: force 8 byte alignment when --no-huge is used
Date: Thu, 24 Jul 2025 02:04:43 +0200 (CEST) [thread overview]
Message-ID: <20250724000443.AE2571241EE@dpdk.org> (raw)
In-Reply-To: <20250724000554.114087-1-drc@linux.ibm.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/155501
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#131: FILE: lib/eal/common/eal_common_trace.c:367:
+ size_t mem_size = trace_mem_sz(trace->buff_len);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#131: FILE: lib/eal/common/eal_common_trace.c:367:
+ size_t mem_size = trace_mem_sz(trace->buff_len);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#132: FILE: lib/eal/common/eal_common_trace.c:368:
+ void *aligned_ptr = NULL;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#132: FILE: lib/eal/common/eal_common_trace.c:368:
+ void *aligned_ptr = NULL;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#133: FILE: lib/eal/common/eal_common_trace.c:369:
+ int ret = posix_memalign(&aligned_ptr, 8, mem_size);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#133: FILE: lib/eal/common/eal_common_trace.c:369:
+ int ret = posix_memalign(&aligned_ptr, 8, mem_size);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#134: FILE: lib/eal/common/eal_common_trace.c:370:
+ header = (ret == 0) ? aligned_ptr : NULL;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#134: FILE: lib/eal/common/eal_common_trace.c:370:
+ header = (ret == 0) ? aligned_ptr : NULL;$
total: 4 errors, 4 warnings, 13 lines checked
next prev parent reply other threads:[~2025-07-24 0:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250724000554.114087-1-drc@linux.ibm.com>
2025-07-23 23:37 ` |SUCCESS| " qemudev
2025-07-23 23:41 ` qemudev
2025-07-24 0:04 ` checkpatch [this message]
2025-07-24 0:48 ` |SUCCESS| pw155501 [PATCH] trace: force 8 byte alignment when --no-h dpdklab
2025-07-24 0:50 ` |PENDING| " dpdklab
2025-07-24 0:58 ` |SUCCESS| " dpdklab
2025-07-24 0:59 ` |PENDING| " dpdklab
2025-07-24 1:01 ` dpdklab
2025-07-24 1:03 ` |SUCCESS| pw155501 [PATCH] trace: force 8 byte alignment when --no-huge is used 0-day Robot
2025-07-24 1:03 ` |SUCCESS| pw155501 [PATCH] trace: force 8 byte alignment when --no-h dpdklab
2025-07-24 1:06 ` dpdklab
2025-07-24 1:07 ` |FAILURE| " dpdklab
2025-07-24 1:12 ` |SUCCESS| " dpdklab
2025-07-24 1:12 ` dpdklab
2025-07-24 1:24 ` dpdklab
2025-07-24 1:31 ` dpdklab
2025-07-24 1:50 ` dpdklab
2025-07-24 4:26 ` dpdklab
2025-07-24 9:01 ` dpdklab
2025-07-24 10:49 ` dpdklab
2025-07-24 10:51 ` dpdklab
2025-07-24 11:10 ` 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=20250724000443.AE2571241EE@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).