From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Wei Hu (Xavier)" <huwei013@chinasoftinc.com>
Subject: [dpdk-test-report] |WARNING| pw80710 [PATCH 1/2] net/hns3: support SVE Rx
Date: Wed, 14 Oct 2020 12:02:28 +0200 (CEST) [thread overview]
Message-ID: <20201014100228.6D5DD1DDFC@dpdk.org> (raw)
In-Reply-To: <20201014100114.26596-2-huwei013@chinasoftinc.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/80710
_coding style issues_
WARNING:TYPO_SPELLING: '2st' may be misspelled - perhaps '2nd'?
#267: FILE: drivers/net/hns3/hns3_rxtx_vec_sve.c:96:
+ 2, 0xffff, 3, 0xffff, /* 2st mbuf: pkt_len and dat_len */
WARNING:TYPO_SPELLING: '3st' may be misspelled - perhaps '3rd'?
#268: FILE: drivers/net/hns3/hns3_rxtx_vec_sve.c:97:
+ 4, 0xffff, 5, 0xffff, /* 3st mbuf: pkt_len and dat_len */
WARNING:TYPO_SPELLING: '2st' may be misspelled - perhaps '2nd'?
#278: FILE: drivers/net/hns3/hns3_rxtx_vec_sve.c:107:
+ 1, 0xffff, /* 2st mbuf: rss */
WARNING:TYPO_SPELLING: '3st' may be misspelled - perhaps '3rd'?
#279: FILE: drivers/net/hns3/hns3_rxtx_vec_sve.c:108:
+ 2, 0xffff, /* 3st mbuf: rss */
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#357: FILE: drivers/net/hns3/hns3_rxtx_vec_sve.c:186:
+ xlen1st = svreinterpret_u64_u16(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#359: FILE: drivers/net/hns3/hns3_rxtx_vec_sve.c:188:
+ xlen2st = svreinterpret_u64_u16(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#361: FILE: drivers/net/hns3/hns3_rxtx_vec_sve.c:190:
+ rss1st = svreinterpret_u64_u32(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#363: FILE: drivers/net/hns3/hns3_rxtx_vec_sve.c:192:
+ rss2st = svreinterpret_u64_u32(
total: 0 errors, 4 warnings, 4 checks, 394 lines checked
parent reply other threads:[~2020-10-14 10:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201014100114.26596-2-huwei013@chinasoftinc.com>]
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=20201014100228.6D5DD1DDFC@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=huwei013@chinasoftinc.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).