From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Su Sai <susai.ss@bytedance.com>
Subject: |WARNING| pw155627 [v2] net/cksum: compute raw cksum for several segments
Date: Fri, 1 Aug 2025 17:27:54 +0200 (CEST) [thread overview]
Message-ID: <20250801152754.3769C125214@dpdk.org> (raw)
In-Reply-To: <CABsP7wMLpN-mggd7dY42YEbq_YH5nz=BQSQHV43yZWhpbDNy=Q@mail.gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/155627
_coding style issues_
ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#111: FILE: :176:
uint32_t off, uint32_t len,
WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#116: FILE: :180:
+ tmp = rte_bswap32(tmp);
WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#126: FILE: :192:
+ *cksum = __rte_raw_cksum_reduce_u64(sum);
WARNING:BLOCK_COMMENT_STYLE: Block comments use * on subsequent lines
#150: FILE: app/test/test_cksum.c:89:
+/* generated in scapy with
+static const char test_cksum_ipv4_tcp_multi_segs[] = {
WARNING:TYPO_SPELLING: 'lenght' may be misspelled - perhaps 'length'?
#178: FILE: app/test/test_cksum.c:117:
+ 61, /* the second seg lenght is odd, test byte order independent */
ERROR:TRAILING_WHITESPACE: trailing whitespace
#205: FILE: app/test/test_cksum.c:272:
+^I$
ERROR:TRAILING_WHITESPACE: trailing whitespace
#210: FILE: app/test/test_cksum.c:277:
+^I^I$
ERROR:TRAILING_WHITESPACE: trailing whitespace
#234: FILE: app/test/test_cksum.c:301:
+^I$
total: 4 errors, 4 warnings, 183 lines checked
next prev parent reply other threads:[~2025-08-01 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABsP7wMLpN-mggd7dY42YEbq_YH5nz=BQSQHV43yZWhpbDNy=Q@mail.gmail.com>
2025-08-01 14:54 ` qemudev
2025-08-01 15:27 ` checkpatch [this message]
2025-08-01 15:41 ` |WARNING| pw155627 [PATCH] " 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=20250801152754.3769C125214@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=susai.ss@bytedance.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).