From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kai Ji <kai.ji@intel.com>
Subject: |WARNING| pw107035 [dpdk-dev v7 04/10] crypto/qat: rework session APIs
Date: Tue, 8 Feb 2022 19:16:51 +0100 (CET) [thread overview]
Message-ID: <20220208181651.986EA120715@dpdk.org> (raw)
In-Reply-To: <20220208181454.69121-5-kai.ji@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/107035
_coding style issues_
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#145: 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'?
#148: 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'?
#151: 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'?
#154: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen2.c:199:
+ header->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#158: 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'?
#161: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen2.c:206:
+ header->serv_specif_flags, 0);
total: 0 errors, 6 warnings, 742 lines checked
parent reply other threads:[~2022-02-08 18:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220208181454.69121-5-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=20220208181651.986EA120715@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).