automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Manish Chopra <manishc@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw73958 [PATCH v2 1/7] lib/librte_pci: add rte_pci_regs.h
Date: Mon, 13 Jul 2020 17:15:51 +0200 (CEST)	[thread overview]
Message-ID: <20200713151551.B722E1D618@dpdk.org> (raw)
In-Reply-To: <20200713151319.17547-2-manishc@marvell.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#254: FILE: lib/librte_pci/rte_pci_regs.h:43:
+#define  PCI_COMMAND_MASTER	0x4	/* Enable bus mastering */

WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#277: FILE: lib/librte_pci/rte_pci_regs.h:66:
+#define  PCI_STATUS_REC_TARGET_ABORT	0x1000 /* Master ack of " */

WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#278: FILE: lib/librte_pci/rte_pci_regs.h:67:
+#define  PCI_STATUS_REC_MASTER_ABORT	0x2000 /* Set on master abort */

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#278: FILE: lib/librte_pci/rte_pci_regs.h:67:
+#define  PCI_STATUS_REC_MASTER_ABORT	0x2000 /* Set on master abort */

WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#375: FILE: lib/librte_pci/rte_pci_regs.h:164:
+#define  PCI_BRIDGE_CTL_MASTER_ABORT	0x20  /* Report master aborts */

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#375: FILE: lib/librte_pci/rte_pci_regs.h:164:
+#define  PCI_BRIDGE_CTL_MASTER_ABORT	0x20  /* Report master aborts */

WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#406: FILE: lib/librte_pci/rte_pci_regs.h:195:
+#define  PCI_CB_BRIDGE_CTL_MASTER_ABORT	0x20

WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#489: FILE: lib/librte_pci/rte_pci_regs.h:278:
+#define  PCI_AGP_COMMAND_RQ_MASK 0xff000000  /* Master: Maximum number of requests */

WARNING:TYPO_SPELLING: 'UNX' may be misspelled - perhaps 'UNIX'?
#650: FILE: lib/librte_pci/rte_pci_regs.h:439:
+#define  PCI_X_STATUS_UNX_SPL	0x00080000	/* Unexpected Split Completion */

WARNING:TYPO_SPELLING: 'UNX' may be misspelled - perhaps 'UNIX'?
#950: FILE: lib/librte_pci/rte_pci_regs.h:739:
+#define  PCI_ERR_UNC_UNX_COMP	0x00010000	/* Unexpected Completion */

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#1057: FILE: lib/librte_pci/rte_pci_regs.h:846:
+#define HT_CAPTYPE_SLAVE	0x00	/* Slave/Primary link configuration */

WARNING:TYPO_SPELLING: 'Slave' may be misspelled - perhaps 'Secondary'?
#1057: FILE: lib/librte_pci/rte_pci_regs.h:846:
+#define HT_CAPTYPE_SLAVE	0x00	/* Slave/Primary link configuration */

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1079: FILE: lib/librte_pci/rte_pci_regs.h:868:
+#define HT_CAP_SIZEOF_LONG	28	/* slave & primary */

total: 0 errors, 13 warnings, 1145 lines checked

           reply	other threads:[~2020-07-13 15:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20200713151319.17547-2-manishc@marvell.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=20200713151551.B722E1D618@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=manishc@marvell.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).