From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wenbo Cao <caowenbo@mucse.com>
Subject: |WARNING| pw129770 [[PATCH v1] 8/8] net/rnp handle device interrupts
Date: Tue, 1 Aug 2023 09:20:27 +0200 (CEST) [thread overview]
Message-ID: <20230801072027.455811206A8@dpdk.org> (raw)
In-Reply-To: <20230801071929.834442-1-caowenbo@mucse.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/129770
_coding style issues_
WARNING:TYPO_SPELLING: 'REMOT' may be misspelled - perhaps 'REMOTE'?
#166: FILE: drivers/net/rnp/base/rnp_mac_regs.h:69:
+#define RNP_MAC_LS_REMOT_FAULT (BIT(25) | BIT(24))
WARNING:TYPO_SPELLING: 'Stip' may be misspelled - perhaps 'Strip'?
#215: FILE: drivers/net/rnp/base/rnp_mac_regs.h:118:
+/* All Vlan Will Stip */
WARNING:TYPO_SPELLING: 'Boradcast' may be misspelled - perhaps 'Broadcast'?
#292: FILE: drivers/net/rnp/base/rnp_mac_regs.h:195:
+/* Tx Good Boradcast Frame Num Base */
WARNING:TYPO_SPELLING: 'Recive' may be misspelled - perhaps 'Receive'?
#334: FILE: drivers/net/rnp/base/rnp_mac_regs.h:237:
+/* Recive Jumbo Frame Error */
WARNING:TYPO_SPELLING: 'parm' may be misspelled - perhaps 'param'?
#411: FILE: drivers/net/rnp/rnp_ethdev.c:603:
+static void rnp_dev_interrupt_handler(void *parm)
WARNING:TYPO_SPELLING: 'parm' may be misspelled - perhaps 'param'?
#413: FILE: drivers/net/rnp/rnp_ethdev.c:605:
+ struct rte_eth_dev *dev = (struct rte_eth_dev *)parm;
WARNING:TYPO_SPELLING: 'linke' may be misspelled - perhaps 'linked'?
#723: FILE: drivers/net/rnp/rnp_mbx_fw.h:112:
+ u16 speed; /* cur port linke speed */
total: 0 errors, 7 warnings, 0 checks, 660 lines checked
next parent reply other threads:[~2023-08-01 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230801071929.834442-1-caowenbo@mucse.com>
2023-08-01 7:20 ` checkpatch [this message]
2023-08-01 7:35 ` 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=20230801072027.455811206A8@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=caowenbo@mucse.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).