From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kai Ji <kai.ji@intel.com>
Subject: |WARNING| pw107819 [dpdk-dev v9 3/9] crypto/qat: rework session functions
Date: Fri, 18 Feb 2022 18:17:47 +0100 (CET) [thread overview]
Message-ID: <20220218171747.C073512336A@dpdk.org> (raw)
In-Reply-To: <20220218171527.56719-4-kai.ji@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/107819
_coding style issues_
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#144: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen2.c:190:
+ ICP_QAT_FW_LA_PROTO_SET(header->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#147: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen2.c:193:
+ header->serv_specif_flags, 0);
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#150: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen2.c:196:
+ ICP_QAT_FW_LA_PROTO_SET(header->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#153: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen2.c:199:
+ header->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#157: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen2.c:203:
+ ICP_QAT_FW_LA_PROTO_SET(header->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#160: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen2.c:206:
+ header->serv_specif_flags, 0);
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#252: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c:156:
+ (void *)&req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#257: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c:161:
+ cipher_param = (void *)&req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#295: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c:199:
+ cipher_param = (void *)&req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#350: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c:254:
+ req->comn_hdr.serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#353: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c:257:
+ req->comn_hdr.serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#536: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c:116:
+ (void *)&req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#538: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c:118:
+ (void *)&req->serv_specif_rqpars;
total: 0 errors, 13 warnings, 901 lines checked
parent reply other threads:[~2022-02-18 17:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220218171527.56719-4-kai.ji@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=20220218171747.C073512336A@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=kai.ji@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).