From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: 苏赛 <susai.ss@bytedance.com>
Subject: |WARNING| pw155604 [PATCH] net/cksum: compute raw cksum for several segments
Date: Thu, 31 Jul 2025 11:53:30 +0200 (CEST) [thread overview]
Message-ID: <20250731095331.078801251A0@dpdk.org> (raw)
In-Reply-To: <CABsP7wOFAsE2-BmnHZW1c3rOkkrUWfox7qrbim6zmP6gbmJqzg@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2413 bytes --]
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/155604
_coding style issues_
ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#103: FILE: :176:
uint32_t off, uint32_t len,
WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#108: FILE: :180:
+ tmp = rte_bswap32(tmp);
WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#118: FILE: :192:
+ *cksum = __rte_raw_cksum_reduce_u64(sum);
ERROR:CODE_INDENT: code indent should use tabs where possible
#152: FILE: lib/net/rte_cksum.h:95:
+ uint32_t tmp;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#152: FILE: lib/net/rte_cksum.h:95:
+ uint32_t tmp;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#154: FILE: lib/net/rte_cksum.h:97:
+ tmp = __rte_raw_cksum_reduce((uint32_t)sum);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#154: FILE: lib/net/rte_cksum.h:97:
+ tmp = __rte_raw_cksum_reduce((uint32_t)sum);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#155: FILE: lib/net/rte_cksum.h:98:
+ tmp += __rte_raw_cksum_reduce((uint32_t)(sum >> 32));$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#155: FILE: lib/net/rte_cksum.h:98:
+ tmp += __rte_raw_cksum_reduce((uint32_t)(sum >> 32));$
ERROR:CODE_INDENT: code indent should use tabs where possible
#156: FILE: lib/net/rte_cksum.h:99:
+ return __rte_raw_cksum_reduce(tmp);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#156: FILE: lib/net/rte_cksum.h:99:
+ return __rte_raw_cksum_reduce(tmp);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#168: FILE: lib/net/rte_cksum.h:141:
+ uint32_t tmp;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#168: FILE: lib/net/rte_cksum.h:141:
+ uint32_t tmp;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#170: FILE: lib/net/rte_cksum.h:143:
+ uint64_t sum;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#170: FILE: lib/net/rte_cksum.h:143:
+ uint64_t sum;$
WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email name mismatch: 'From: "苏赛" <susai.ss@bytedance.com>' != 'Signed-off-by: Su Sai <susai.ss@bytedance.com>'
total: 7 errors, 9 warnings, 58 lines checked
next prev parent reply other threads:[~2025-07-31 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABsP7wOFAsE2-BmnHZW1c3rOkkrUWfox7qrbim6zmP6gbmJqzg@mail.gmail.com>
2025-07-31 9:50 ` qemudev
2025-07-31 9:53 ` checkpatch [this message]
2025-07-31 10:19 ` dpdklab
2025-07-31 11:46 ` qemudev
2025-08-01 2:42 ` qemudev
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=20250731095331.078801251A0@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).