From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wenbo Cao <caowenbo@mucse.com>
Subject: |WARNING| pw129788 [[PATCH v1] 5/8] net/rnp add reset code for Chip Init process
Date: Tue, 1 Aug 2023 12:34:13 +0200 (CEST) [thread overview]
Message-ID: <20230801103413.F29A21206A8@dpdk.org> (raw)
In-Reply-To: <20230801064346.805294-6-caowenbo@mucse.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/129788
_coding style issues_
WARNING:TYPO_SPELLING: 'CLER' may be misspelled - perhaps 'CLEAR'?
#179: FILE: drivers/net/rnp/base/rnp_dma_regs.h:33:
+#define RNP_DMA_INT_CLER(qid) _RING_(0x0028 + 0x100 * (qid))
WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#264: FILE: drivers/net/rnp/base/rnp_eth_regs.h:39:
+/* This Just VLAN Master Switch */
WARNING:TYPO_SPELLING: 'INDEPEND' may be misspelled - perhaps 'INDEPENDENT'?
#464: FILE: drivers/net/rnp/rnp.h:18:
+ RNP_SHARE_INDEPEND,
WARNING:TYPO_SPELLING: 'INDEPEND' may be misspelled - perhaps 'INDEPENDENT'?
#577: FILE: drivers/net/rnp/rnp_ethdev.c:121:
+ adapter->s_mode = RNP_SHARE_INDEPEND;
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#683: FILE: drivers/net/rnp/rnp_mbx_fw.c:2:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'capablity' may be misspelled - perhaps 'capability'?
#790: FILE: drivers/net/rnp/rnp_mbx_fw.c:109:
+static int rnp_fw_get_capablity(struct rte_eth_dev *dev,
WARNING:TYPO_SPELLING: 'capablity' may be misspelled - perhaps 'capability'?
#830: FILE: drivers/net/rnp/rnp_mbx_fw.c:149:
+ err = rnp_fw_get_capablity(dev, &ablity);
WARNING:TYPO_SPELLING: 'FAILD' may be misspelled - perhaps 'FAILED'?
#977: FILE: drivers/net/rnp/rnp_mbx_fw.h:34:
+ EVT_MODULE_QUALIFICATION_FAILD = 8,
total: 0 errors, 8 warnings, 0 checks, 970 lines checked
prev parent reply other threads:[~2023-08-01 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230801064346.805294-6-caowenbo@mucse.com>
2023-08-01 10:24 ` qemudev
2023-08-01 10:34 ` checkpatch [this message]
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=20230801103413.F29A21206A8@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).