From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wenbo Cao <caowenbo@mucse.com>
Subject: |WARNING| pw129829 [PATCH v2 3/8] net/rnp: add device init and uninit
Date: Wed, 2 Aug 2023 10:16:04 +0200 (CEST) [thread overview]
Message-ID: <20230802081604.376F51206A8@dpdk.org> (raw)
In-Reply-To: <20230802081106.2340406-4-caowenbo@mucse.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/129829
_coding style issues_
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#137: FILE: drivers/net/rnp/rnp.h:26:
+ struct rte_eth_dev *eth_dev; /* master eth_dev */
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#210: FILE: drivers/net/rnp/rnp_ethdev.c:57:
+rnp_alloc_eth_port(struct rte_pci_device *master_pci, char *name)
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#224: FILE: drivers/net/rnp/rnp_ethdev.c:71:
+ master_pci->device.numa_node);
WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#281: FILE: drivers/net/rnp/rnp_ethdev.c:128:
+ /* port 0 resource has been alloced When Probe */
WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#339: FILE: drivers/net/rnp/rnp_ethdev.c:184:
+ "Isn't Master Ethdev
");
WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#348: FILE: drivers/net/rnp/rnp_ethdev.c:193:
+ /* Just Release Not Master Port Alloced By PMD */
WARNING:TYPO_SPELLING: 'Alloced' may be misspelled - perhaps 'Allocated'?
#348: FILE: drivers/net/rnp/rnp_ethdev.c:193:
+ /* Just Release Not Master Port Alloced By PMD */
total: 0 errors, 7 warnings, 0 checks, 338 lines checked
parent reply other threads:[~2023-08-02 8:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230802081106.2340406-4-caowenbo@mucse.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=20230802081604.376F51206A8@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).