From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kai Ji <kai.ji@intel.com>
Subject: |WARNING| pw107755 [dpdk-dev v8 02/10] crypto/qat: sym build op request specific implementation
Date: Thu, 17 Feb 2022 17:30:18 +0100 (CET) [thread overview]
Message-ID: <20220217163018.84A0D12336A@dpdk.org> (raw)
In-Reply-To: <20220217162909.22713-3-kai.ji@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/107755
_coding style issues_
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#634: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gens.h:555:
+ qat_req->comn_hdr.serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#657: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gens.h:578:
+ cipher_param = (void *)&req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#676: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gens.h:597:
+ cipher_param = (void *)&req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#694: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gens.h:615:
+ req->comn_hdr.serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#724: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gens.h:645:
+ cipher_param = (void *)&req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#784: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gens.h:705:
+ ICP_QAT_FW_LA_DIGEST_IN_BUFFER_SET(header->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#800: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gens.h:721:
+ (void *)&req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#802: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gens.h:723:
+ (void *)((uint8_t *)&req->serv_specif_rqpars +
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#815: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gens.h:736:
+ req->comn_hdr.serv_specif_flags,
total: 0 errors, 9 warnings, 1147 lines checked
parent reply other threads:[~2022-02-17 16:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220217162909.22713-3-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=20220217163018.84A0D12336A@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).