From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Xueming Li <xuemingl@nvidia.com>
Subject: [dpdk-test-report] |WARNING| pw88950 [RFC] bus/auxiliary: introduce auxiliary bus
Date: Thu, 11 Mar 2021 14:03:10 +0100 (CET) [thread overview]
Message-ID: <20210311130310.D50F7134F@dpdk.org> (raw)
In-Reply-To: <20210311130113.31382-1-xuemingl@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/88950
_coding style issues_
WARNING:TYPO_SPELLING: 'AUXILIAR' may be misspelled - perhaps 'AUXILIARY'?
#195: FILE: drivers/bus/auxiliary/auxiliary_common.c:97:
+ AUXILIAR_LOG(DEBUG, "Auxiliary device %s on NUMA socket %i
",
WARNING:TYPO_SPELLING: 'AUXILIAR' may be misspelled - perhaps 'AUXILIARY'?
#201: FILE: drivers/bus/auxiliary/auxiliary_common.c:103:
+ AUXILIAR_LOG(INFO, " Device is blocked, not initializing
");
WARNING:TYPO_SPELLING: 'AUXILIAR' may be misspelled - perhaps 'AUXILIARY'?
#206: FILE: drivers/bus/auxiliary/auxiliary_common.c:108:
+ AUXILIAR_LOG(WARNING, " Invalid NUMA socket, default to 0
");
WARNING:TYPO_SPELLING: 'AUXILIAR' may be misspelled - perhaps 'AUXILIARY'?
#212: FILE: drivers/bus/auxiliary/auxiliary_common.c:114:
+ AUXILIAR_LOG(DEBUG, " Device %s is already probed
",
WARNING:TYPO_SPELLING: 'AUXILIAR' may be misspelled - perhaps 'AUXILIARY'?
#217: FILE: drivers/bus/auxiliary/auxiliary_common.c:119:
+ AUXILIAR_LOG(DEBUG, " Probe driver: %s
", dr->driver.name);
WARNING:TYPO_SPELLING: 'AUXILIAR' may be misspelled - perhaps 'AUXILIARY'?
#225: FILE: drivers/bus/auxiliary/auxiliary_common.c:127:
+ AUXILIAR_LOG(ERR, " Expecting VA IOVA mode but current mode is PA, not initializing
");
WARNING:TYPO_SPELLING: 'AUXILIAR' may be misspelled - perhaps 'AUXILIARY'?
#232: FILE: drivers/bus/auxiliary/auxiliary_common.c:134:
+ AUXILIAR_LOG(INFO, "Probe auxiliary driver: %s device: %s (socket %i)
",
WARNING:TYPO_SPELLING: 'AUXILIAR' may be misspelled - perhaps 'AUXILIARY'?
#259: FILE: drivers/bus/auxiliary/auxiliary_common.c:161:
+ AUXILIAR_LOG(DEBUG, "Auxiliary device %s on NUMA socket %i
",
WARNING:TYPO_SPELLING: 'AUXILIAR' may be misspelled - perhaps 'AUXILIARY'?
#262: FILE: drivers/bus/auxiliary/auxiliary_common.c:164:
+ AUXILIAR_LOG(DEBUG, " remove driver: %s %s
",
WARNING:TYPO_SPELLING: 'AUXILIAR' may be misspelled - perhaps 'AUXILIARY'?
#327: FILE: drivers/bus/auxiliary/auxiliary_common.c:229:
+ AUXILIAR_LOG(ERR, "Requested device %s cannot be used
",
WARNING:TYPO_SPELLING: 'AUXILIAR' may be misspelled - perhaps 'AUXILIARY'?
#689: FILE: drivers/bus/auxiliary/linux/auxiliary.c:111:
+ AUXILIAR_LOG(ERR, "%s(): opendir failed: %s
",
WARNING:TYPO_SPELLING: 'AUXILIAR' may be misspelled - perhaps 'AUXILIARY'?
#767: FILE: drivers/bus/auxiliary/private.h:16:
+#define AUXILIAR_LOG(level, fmt, args...) \
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#1047: FILE: drivers/bus/auxiliary/rte_bus_auxiliary.h:171:
+#define RTE_PMD_REGISTER_AUXILIARY(nm, auxiliary_drv) \
+ RTE_INIT(auxiliaryinitfn_##nm) \
+ { \
+ (auxiliary_drv).driver.name = RTE_STR(nm); \
+ rte_auxiliary_register(&auxiliary_drv); \
+ } \
+ RTE_PMD_EXPORT_NAME(nm, __COUNTER__)
total: 1 errors, 12 warnings, 969 lines checked
parent reply other threads:[~2021-03-11 13:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210311130113.31382-1-xuemingl@nvidia.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=20210311130310.D50F7134F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.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).