From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: |WARNING| pw130564 [PATCH v2 01/15] drivers: remove duplicated PCI master control
Date: Mon, 21 Aug 2023 13:37:49 +0200 (CEST) [thread overview]
Message-ID: <20230821113749.DDC881206AB@dpdk.org> (raw)
In-Reply-To: <20230821113549.3191921-2-david.marchand@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/130564
_coding style issues_
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#51:
Subject: [PATCH v2 01/15] drivers: remove duplicated PCI master control
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#139: FILE: drivers/bus/pci/linux/pci_uio.c:272:
+ if (rte_pci_set_bus_master(dev, true)) {
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#196: FILE: drivers/bus/pci/linux/pci_vfio.c:502:
+ if (rte_pci_set_bus_master(dev, true)) {
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#205: FILE: drivers/bus/pci/linux/pci_vfio.c:1192:
+ if (rte_pci_set_bus_master(dev, false)) {
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#248: FILE: drivers/net/hns3/hns3_ethdev_vf.c:2120:
+ ret = rte_pci_set_bus_master(pci_dev, true);
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#280: FILE: drivers/net/ngbe/base/ngbe_hw.c:1066:
+ if (rte_pci_set_bus_master(pci_dev, enable) < 0) {
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#281: FILE: drivers/net/ngbe/base/ngbe_hw.c:1067:
+ DEBUGOUT("Cannot configure PCI bus master
");
total: 0 errors, 7 warnings, 0 checks, 181 lines checked
parent reply other threads:[~2023-08-21 11:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230821113549.3191921-2-david.marchand@redhat.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=20230821113749.DDC881206AB@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=david.marchand@redhat.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).