From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Morten Brørup" <mb@smartsharesystems.com>
Subject: |WARNING| pw121447 [PATCH v3 2/2] net/bnx2x: fix warnings about rte_memcopy lengths
Date: Wed, 28 Dec 2022 11:28:13 +0100 (CET) [thread overview]
Message-ID: <20221228102813.16C8F122EC0@dpdk.org> (raw)
In-Reply-To: <20221228102708.93208-2-mb@smartsharesystems.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/121447
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#82: FILE: drivers/net/bnx2x/bnx2x_stats.c:822:
+ rte_memcpy((struct mac_stx *)&(estats->rx_stat_ifhcinbadoctets_hi), &(pstats->mac_stx[1]),$
CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around estats->rx_stat_ifhcinbadoctets_hi
#82: FILE: drivers/net/bnx2x/bnx2x_stats.c:822:
+ rte_memcpy((struct mac_stx *)&(estats->rx_stat_ifhcinbadoctets_hi), &(pstats->mac_stx[1]),
CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around pstats->mac_stx[1]
#82: FILE: drivers/net/bnx2x/bnx2x_stats.c:822:
+ rte_memcpy((struct mac_stx *)&(estats->rx_stat_ifhcinbadoctets_hi), &(pstats->mac_stx[1]),
CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around sc->port.old_nig_stats.egress_mac_pkt0_lo
#91: FILE: drivers/net/bnx2x/bnx2x_stats.c:1495:
+ (uint32_t *)&(sc->port.old_nig_stats.egress_mac_pkt0_lo), 2);
CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around sc->port.old_nig_stats.egress_mac_pkt1_lo
#94: FILE: drivers/net/bnx2x/bnx2x_stats.c:1497:
+ (uint32_t *)&(sc->port.old_nig_stats.egress_mac_pkt1_lo), 2);
total: 0 errors, 1 warnings, 4 checks, 27 lines checked
next prev parent reply other threads:[~2022-12-28 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221228102708.93208-2-mb@smartsharesystems.com>
2022-12-28 10:19 ` |SUCCESS| pw121446-121447 " qemudev
2022-12-28 10:23 ` qemudev
2022-12-28 10:28 ` checkpatch [this message]
2022-12-28 11:39 ` |SUCCESS| pw121447 " 0-day Robot
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=20221228102813.16C8F122EC0@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=mb@smartsharesystems.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).