From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-test-report] |WARNING| pw97702 [PATCH 3/4] crypto/qat: move capabilities initialization to spec files
Date: Wed, 1 Sep 2021 16:48:26 +0200 (CEST) [thread overview]
Message-ID: <20210901144826.9A97E122E33@dpdk.org> (raw)
In-Reply-To: <20210901144729.26784-4-arkadiuszx.kusztal@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/97702
_coding style issues_
WARNING:TYPO_SPELLING: 'capabilites' may be misspelled - perhaps 'capabilities'?
#53:
Move capabilites static struct to particular generations into
WARNING:TYPO_SPELLING: 'capabilties' may be misspelled - perhaps 'capabilities'?
#89: FILE: drivers/crypto/qat/dev/qat_sym_pmd_gen1.c:59:
+qat_capabilities_info get_capabilties_gen1(
WARNING:TYPO_SPELLING: 'capabilties' may be misspelled - perhaps 'capabilities'?
#102: FILE: drivers/crypto/qat/dev/qat_sym_pmd_gen1.c:71:
+ .qat_sym_get_capabilities = get_capabilties_gen1,
WARNING:MISSING_EOF_NEWLINE: adding a line without newline at end of file
#109: FILE: drivers/crypto/qat/dev/qat_sym_pmd_gen1.c:78:
+}
WARNING:TYPO_SPELLING: 'capabilties' may be misspelled - perhaps 'capabilities'?
#137: FILE: drivers/crypto/qat/dev/qat_sym_pmd_gen2.c:85:
+qat_capabilities_info get_capabilties_gen2(
WARNING:TYPO_SPELLING: 'capabilties' may be misspelled - perhaps 'capabilities'?
#148: FILE: drivers/crypto/qat/dev/qat_sym_pmd_gen2.c:96:
+ .qat_sym_get_capabilities = get_capabilties_gen2,
WARNING:TYPO_SPELLING: 'capabilties' may be misspelled - perhaps 'capabilities'?
#180: FILE: drivers/crypto/qat/dev/qat_sym_pmd_gen3.c:44:
+qat_capabilities_info get_capabilties_gen3(
WARNING:TYPO_SPELLING: 'capabilties' may be misspelled - perhaps 'capabilities'?
#191: FILE: drivers/crypto/qat/dev/qat_sym_pmd_gen3.c:55:
+ .qat_sym_get_capabilities = get_capabilties_gen3,
WARNING:TYPO_SPELLING: 'capabilties' may be misspelled - perhaps 'capabilities'?
#222: FILE: drivers/crypto/qat/dev/qat_sym_pmd_gen4.c:85:
+qat_capabilities_info get_capabilties_gen4(
WARNING:TYPO_SPELLING: 'capabilties' may be misspelled - perhaps 'capabilities'?
#234: FILE: drivers/crypto/qat/dev/qat_sym_pmd_gen4.c:97:
+ .qat_sym_get_capabilities = get_capabilties_gen4,
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#372: FILE: drivers/crypto/qat/qat_sym_pmd.h:35:
+rte_cryptodev_ops *QAT_CRYPTODEV_OPS[];
^
total: 1 errors, 10 warnings, 281 lines checked
parent reply other threads:[~2021-09-01 14:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210901144729.26784-4-arkadiuszx.kusztal@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=20210901144826.9A97E122E33@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=arkadiuszx.kusztal@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).