From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Adam Dybkowski <adamx.dybkowski@intel.com>
Subject: [dpdk-test-report] |WARNING| pw88581 [PATCH v2 1/1] crypto/qat: support Single-Pass GMAC on QAT GEN3
Date: Fri, 5 Mar 2021 15:17:21 +0100 (CET) [thread overview]
Message-ID: <20210305141721.484ED9A8@dpdk.org> (raw)
In-Reply-To: <20210305141641.16707-2-adamx.dybkowski@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/88581
_coding style issues_
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#112: FILE: drivers/crypto/qat/qat_sym.c:162:
+ (void *) &qat_req->serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#343: FILE: drivers/crypto/qat/qat_sym_session.c:540:
+ (void *) &session->fw_req2.serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#361: FILE: drivers/crypto/qat/qat_sym_session.c:558:
+ session->fw_req2.comn_hdr.serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#364: FILE: drivers/crypto/qat/qat_sym_session.c:561:
+ session->fw_req2.comn_hdr.serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#367: FILE: drivers/crypto/qat/qat_sym_session.c:564:
+ session->fw_req2.comn_hdr.serv_specif_flags,
total: 0 errors, 5 warnings, 327 lines checked
next parent reply other threads:[~2021-03-05 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210305141641.16707-2-adamx.dybkowski@intel.com>
2021-03-05 14:17 ` checkpatch [this message]
2021-03-05 15:56 ` [dpdk-test-report] |SUCCESS| pw88581 " 0-day Robot
2021-03-05 16:57 ` [dpdk-test-report] |SUCCESS| pw88581 [dpdk-dev] [PATCH v2 1/1] " 0-day Robot
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=20210305141721.484ED9A8@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=adamx.dybkowski@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).