automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wei Huang <wei.huang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw85891 [PATCH v2 3/4] raw/ifpga: add opae API for Cyborg
Date: Wed, 30 Dec 2020 03:54:56 +0100 (CET)	[thread overview]
Message-ID: <20201230025456.8FFAF4C8F@dpdk.org> (raw)
In-Reply-To: <1609296722-3753-4-git-send-email-wei.huang@intel.com>

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

_coding style issues_


ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#1372: FILE: drivers/raw/ifpga/ifpga_opae_api.c:1278:
+#define PCI_EXT_CAP_ID(hdr)		(int)(hdr & 0x0000ffff)

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1652: FILE: drivers/raw/ifpga/ifpga_opae_api.c:1558:
+	pcidev_id peer_master = NULL;

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1683: FILE: drivers/raw/ifpga/ifpga_opae_api.c:1589:
+		peer_master = &peer[0];

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1684: FILE: drivers/raw/ifpga/ifpga_opae_api.c:1590:
+		ret = opae_get_parent(peer_master, &peer_parent);

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1740: FILE: drivers/raw/ifpga/ifpga_opae_api.c:1646:
+				if (peer_master) {

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1742: FILE: drivers/raw/ifpga/ifpga_opae_api.c:1648:
+						peer_master);

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1745: FILE: drivers/raw/ifpga/ifpga_opae_api.c:1651:
+							peer_master->bdf);

total: 1 errors, 6 warnings, 2278 lines checked

           reply	other threads:[~2020-12-30  2:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1609296722-3753-4-git-send-email-wei.huang@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=20201230025456.8FFAF4C8F@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=wei.huang@intel.com \
    /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).