From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Aman Kumar <aman.kumar@vvdntech.in>
Subject: |WARNING| pw113726 [RFC PATCH 08/29] net/qdma: qdma hardware initialization
Date: Wed, 6 Jul 2022 11:44:55 +0200 (CEST) [thread overview]
Message-ID: <20220706094455.40B04120D82@dpdk.org> (raw)
In-Reply-To: <20220706075219.517046-9-aman.kumar@vvdntech.in>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/113726
_coding style issues_
WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#171: FILE: drivers/net/qdma/qdma_common.c:218:
+ /* Find AXI Master Lite(user bar) */
WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#183: FILE: drivers/net/qdma/qdma_common.c:230:
+ PMD_DRV_LOG(INFO, "Cannot find AXI Master Lite BAR");
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#398: FILE: drivers/net/qdma/qdma_ethdev.c:442:
+ /* Create master resource node for queue management on the given
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#413: FILE: drivers/net/qdma/qdma_ethdev.c:456:
+ ret = qdma_master_resource_create(pci_dev->addr.bus, max_pci_bus,
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#427: FILE: drivers/net/qdma/qdma_ethdev.c:470:
+ * done by the master PF
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#469: FILE: drivers/net/qdma/qdma_ethdev.c:512:
+ dma_priv->is_master = 1;
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#497: FILE: drivers/net/qdma/qdma_ethdev.c:571:
+ if (qdma_dev->is_master)
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#503: FILE: drivers/net/qdma/qdma_ethdev.c:577:
+ qdma_master_resource_destroy(qdma_dev->dma_device_index);
total: 0 errors, 8 warnings, 0 checks, 398 lines checked
parent reply other threads:[~2022-07-06 9:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220706075219.517046-9-aman.kumar@vvdntech.in>]
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=20220706094455.40B04120D82@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=aman.kumar@vvdntech.in \
--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).