automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Haiyue Wang <haiyue.wang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw93381 [PATCH v7 3/3] net/i40e: enable PCI bus master after reset
Date: Mon, 24 May 2021 03:46:28 +0200 (CEST)	[thread overview]
Message-ID: <20210524014628.571BC122E2C@dpdk.org> (raw)
In-Reply-To: <20210524012346.496560-4-haiyue.wang@intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/93381

_coding style issues_


WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#46: 
Subject: [dpdk-dev] [PATCH v7 3/3] net/i40e: enable PCI bus master after

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#63: 
master will be cleared, the VF will be not allowed to issue any Memory

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'?
#109: FILE: drivers/net/i40e/i40e_ethdev_vf.c:2496:
+	 * master mode, and the driver will fail to recover from the reset. Fix

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#111: FILE: drivers/net/i40e/i40e_ethdev_vf.c:2498:
+	 * the bus master bit will not be disabled, and this call will have no

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#114: FILE: drivers/net/i40e/i40e_ethdev_vf.c:2501:
+	if (vf->vf_reset && !rte_pci_set_bus_master(pci_dev, true))

total: 0 errors, 6 warnings, 0 checks, 37 lines checked

       reply	other threads:[~2021-05-24  1:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210524012346.496560-4-haiyue.wang@intel.com>
2021-05-24  1:46 ` checkpatch [this message]
2021-05-24  2:57 ` [dpdk-test-report] |SUCCESS| pw93381 [dpdk-dev] " 0-day Robot

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=20210524014628.571BC122E2C@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).