From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Haiyue Wang <haiyue.wang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw93376 [PATCH v6 2/3] net/iavf: enable PCI bus master after reset
Date: Sun, 23 May 2021 14:08:24 +0200 (CEST) [thread overview]
Message-ID: <20210523120824.8585C122E28@dpdk.org> (raw)
In-Reply-To: <20210523114609.448092-3-haiyue.wang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/93376
_coding style issues_
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#46:
Subject: [dpdk-dev] [PATCH v6 2/3] net/iavf: enable PCI bus master after
WARNING:TYPO_SPELLING: 'triggerred' may be misspelled - perhaps 'triggered'?
#62:
The VF reset can be triggerred by the PF reset event, in this case, the
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#63:
PCI bus master will be cleared, then the VF is not allowed to issue any
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#66:
So after the reset event is detected, always enable the PCI bus master.
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#86: FILE: drivers/net/iavf/iavf_ethdev.c:2361:
+ * master mode, and the driver will fail to recover from the reset. Fix
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#88: FILE: drivers/net/iavf/iavf_ethdev.c:2363:
+ * the bus master bit will not be disabled, and this call will have no
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#91: FILE: drivers/net/iavf/iavf_ethdev.c:2366:
+ if (vf->vf_reset && !rte_pci_set_bus_master(pci_dev, true))
total: 0 errors, 7 warnings, 0 checks, 16 lines checked
parent reply other threads:[~2021-05-23 12:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210523114609.448092-3-haiyue.wang@intel.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=20210523120824.8585C122E28@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=haiyue.wang@intel.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).