From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chenbo Xia <chenbo.xia@intel.com>
Subject: [dpdk-test-report] |WARNING| pw99257 [PATCH v2 7/7] bus/pci: remove ABIs in PCI bus
Date: Sat, 18 Sep 2021 04:41:31 +0200 (CEST) [thread overview]
Message-ID: <20210918024131.81B24122EE7@dpdk.org> (raw)
In-Reply-To: <20210918022443.12719-8-chenbo.xia@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/99257
_coding style issues_
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#493: FILE: drivers/bus/pci/pci_driver.h:96:
+#define RTE_PCI_DEVICE(vend, dev) \
+ RTE_CLASS_ANY_ID, \
+ (vend), \
+ (dev), \
+ RTE_PCI_ANY_ID, \
+ RTE_PCI_ANY_ID
WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#644: FILE: drivers/bus/pci/pci_driver.h:247:
+ * Enables/Disables Bus Master for device's PCI command register.
WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#649: FILE: drivers/bus/pci/pci_driver.h:252:
+ * Enable or disable Bus Master.
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#655: FILE: drivers/bus/pci/pci_driver.h:258:
+int rte_pci_set_bus_master(struct rte_pci_device *dev, bool enable);
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#668: FILE: drivers/bus/pci/pci_driver.h:271:
+#define RTE_PMD_REGISTER_PCI(nm, pci_drv) \
+RTE_INIT(pciinitfn_ ##nm) \
+{\
+ (pci_drv).driver.name = RTE_STR(nm);\
+ rte_pci_register(&pci_drv); \
+} \
+RTE_PMD_EXPORT_NAME(nm, __COUNTER__)
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1262: FILE: drivers/bus/pci/version.map:29:
+ rte_pci_set_bus_master;
total: 2 errors, 4 warnings, 1833 lines checked
next parent reply other threads:[~2021-09-18 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210918022443.12719-8-chenbo.xia@intel.com>
2021-09-18 2:41 ` checkpatch [this message]
2021-09-18 3:40 ` [dpdk-test-report] |SUCCESS| pw99257 [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=20210918024131.81B24122EE7@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=chenbo.xia@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).