From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <guyk@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw80359 [PATCH v2 2/4] regex/octeontx2: add build infra and device support
Date: Mon, 12 Oct 2020 13:35:21 +0200 (CEST) [thread overview]
Message-ID: <20201012113521.B70831D6DD@dpdk.org> (raw)
In-Reply-To: <20201012113135.19476-3-guyk@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/80359
_coding style issues_
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#1354: FILE: drivers/regex/octeontx2/otx2_regexdev_compiler.c:24:
+ struct rxp_blacklist_data_sample *blacklist_sample_data = NULL;
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#1354: FILE: drivers/regex/octeontx2/otx2_regexdev_compiler.c:24:
+ struct rxp_blacklist_data_sample *blacklist_sample_data = NULL;
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#1373: FILE: drivers/regex/octeontx2/otx2_regexdev_compiler.c:43:
+ float set_auto_blacklist = 0;
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#1424: FILE: drivers/regex/octeontx2/otx2_regexdev_compiler.c:94:
+ blacklist_sample_data,
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#1430: FILE: drivers/regex/octeontx2/otx2_regexdev_compiler.c:100:
+ set_auto_blacklist,
WARNING:TYPO_SPELLING: 'QUE' may be misspelled - perhaps 'QUEUE'?
#1800: FILE: drivers/regex/octeontx2/otx2_regexdev_hw_access.h:45:
+#define OTX2_REE_AF_QUE_SBUF_CTL(a) (0x1200ull | (uint64_t)(a) << 3)
total: 0 errors, 6 warnings, 2237 lines checked
parent reply other threads:[~2020-10-12 11:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201012113135.19476-3-guyk@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=20201012113521.B70831D6DD@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=guyk@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).