From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Fan Zhang <roy.fan.zhang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw101657 [dpdk-dev v3 10/10] common/qat: unify naming conventions in qat functions
Date: Thu, 14 Oct 2021 18:21:39 +0200 (CEST) [thread overview]
Message-ID: <20211014162139.71DFC121D26@dpdk.org> (raw)
In-Reply-To: <20211014161137.1405168-11-roy.fan.zhang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/101657
_coding style issues_
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1057: FILE: drivers/crypto/qat/qat_sym_session.c:510:
+ ICP_QAT_FW_LA_PROTO_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1061: FILE: drivers/crypto/qat/qat_sym_session.c:513:
+ qat_fw_hdr->serv_specif_flags, 0);
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1065: FILE: drivers/crypto/qat/qat_sym_session.c:516:
+ ICP_QAT_FW_LA_PROTO_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1069: FILE: drivers/crypto/qat/qat_sym_session.c:519:
+ qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1074: FILE: drivers/crypto/qat/qat_sym_session.c:523:
+ ICP_QAT_FW_LA_PROTO_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1078: FILE: drivers/crypto/qat/qat_sym_session.c:526:
+ qat_fw_hdr->serv_specif_flags, 0);
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1700: FILE: drivers/crypto/qat/qat_sym_session.c:1485:
+ ICP_QAT_FW_LA_PARTIAL_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1703: FILE: drivers/crypto/qat/qat_sym_session.c:1487:
+ ICP_QAT_FW_LA_CIPH_IV_FLD_FLAG_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1710: FILE: drivers/crypto/qat/qat_sym_session.c:1492:
+ ICP_QAT_FW_LA_PROTO_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1715: FILE: drivers/crypto/qat/qat_sym_session.c:1496:
+ ICP_QAT_FW_LA_PROTO_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1720: FILE: drivers/crypto/qat/qat_sym_session.c:1500:
+ ICP_QAT_FW_LA_PROTO_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1725: FILE: drivers/crypto/qat/qat_sym_session.c:1504:
+ ICP_QAT_FW_LA_PROTO_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1730: FILE: drivers/crypto/qat/qat_sym_session.c:1508:
+ ICP_QAT_FW_LA_ZUC_3G_PROTO_FLAG_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1740: FILE: drivers/crypto/qat/qat_sym_session.c:1516:
+ qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1747: FILE: drivers/crypto/qat/qat_sym_session.c:1521:
+ qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1756: FILE: drivers/crypto/qat/qat_sym_session.c:1527:
+ ICP_QAT_FW_LA_RET_AUTH_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1759: FILE: drivers/crypto/qat/qat_sym_session.c:1529:
+ ICP_QAT_FW_LA_CMP_AUTH_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1764: FILE: drivers/crypto/qat/qat_sym_session.c:1532:
+ ICP_QAT_FW_LA_RET_AUTH_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1767: FILE: drivers/crypto/qat/qat_sym_session.c:1534:
+ ICP_QAT_FW_LA_CMP_AUTH_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1772: FILE: drivers/crypto/qat/qat_sym_session.c:1538:
+ ICP_QAT_FW_LA_RET_AUTH_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1775: FILE: drivers/crypto/qat/qat_sym_session.c:1540:
+ ICP_QAT_FW_LA_CMP_AUTH_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1783: FILE: drivers/crypto/qat/qat_sym_session.c:1546:
+ qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1788: FILE: drivers/crypto/qat/qat_sym_session.c:1550:
+ ICP_QAT_FW_LA_UPDATE_STATE_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1791: FILE: drivers/crypto/qat/qat_sym_session.c:1552:
+ ICP_QAT_FW_LA_DIGEST_IN_BUFFER_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1825: FILE: drivers/crypto/qat/qat_sym_session.c:1571:
+ &qat_session->fw_req.serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1829: FILE: drivers/crypto/qat/qat_sym_session.c:1574:
+ &qat_session->fw_req.serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1846: FILE: drivers/crypto/qat/qat_sym_session.c:1586:
+ ICP_QAT_FW_LA_RET_AUTH_SET(qat_fw_hdr->serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#1849: FILE: drivers/crypto/qat/qat_sym_session.c:1588:
+ ICP_QAT_FW_LA_CMP_AUTH_SET(qat_fw_hdr->serv_specif_flags,
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (16, 32)
#1888: FILE: drivers/crypto/qat/qat_sym_session.c:1615:
+ if (qat_session->qat_cipher_alg ==
[...]
+ qat_session->qat_dir = ICP_QAT_HW_CIPHER_DECRYPT;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#2145: FILE: drivers/crypto/qat/qat_sym_session.c:1773:
+ ((char *)&qat_fw_req->serv_specif_rqpars +
total: 0 errors, 30 warnings, 2453 lines checked
next parent reply other threads:[~2021-10-14 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211014161137.1405168-11-roy.fan.zhang@intel.com>
2021-10-14 16:21 ` checkpatch [this message]
2021-10-14 16:59 ` [dpdk-test-report] |FAILURE| pw101657 [dpdk-dev] " 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=20211014162139.71DFC121D26@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).