From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Fan Zhang <roy.fan.zhang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw80302 [dpdk-dev v13 3/4] crypto/qat: add raw crypto data-path API support
Date: Sun, 11 Oct 2020 02:40:20 +0200 (CEST) [thread overview]
Message-ID: <20201011004020.352651D50F@dpdk.org> (raw)
In-Reply-To: <20201011003854.54947-4-roy.fan.zhang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/80302
_coding style issues_
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#232: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:82:
+ qat_req->comn_hdr.serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#263: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:113:
+ (void *)&req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#265: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:115:
+ (void *)((uint8_t *)&req->serv_specif_rqpars +
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#278: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:128:
+ req->comn_hdr.serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#460: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:310:
+ cipher_param = (void *)&req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#561: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:411:
+ cipher_param = (void *)&req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#579: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:429:
+ req->comn_hdr.serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#687: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:537:
+ cipher_param = (void *)&req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#757: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:607:
+ header->serv_specif_flags,
total: 0 errors, 9 warnings, 1026 lines checked
parent reply other threads:[~2020-10-11 0:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201011003854.54947-4-roy.fan.zhang@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=20201011004020.352651D50F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=roy.fan.zhang@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).