From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ciara Power <ciara.power@intel.com>
Subject: |WARNING| pw137516 [PATCH v7 2/3] crypto/qat: update headers for GEN LCE support
Date: Thu, 29 Feb 2024 19:44:21 +0100 (CET) [thread overview]
Message-ID: <20240229184421.3C07F12232A@dpdk.org> (raw)
In-Reply-To: <20240229184347.2496000-3-ciara.power@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/137516
_coding style issues_
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#291: FILE: drivers/crypto/qat/qat_sym_session.c:2012:
+ ICP_QAT_FW_SYM_AEAD_ALGO_SET(header->serv_specif_flags, QAT_LA_CRYPTO_AEAD_AES_GCM_GEN_LCE);
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#292: FILE: drivers/crypto/qat/qat_sym_session.c:2013:
+ ICP_QAT_FW_SYM_IV_SIZE_SET(header->serv_specif_flags, ICP_QAT_FW_LA_GCM_IV_LEN_12_OCTETS);
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#293: FILE: drivers/crypto/qat/qat_sym_session.c:2014:
+ ICP_QAT_FW_SYM_IV_IN_DESC_FLAG_SET(header->serv_specif_flags,
WARNING:BRACES: braces {} are not necessary for any arm of this statement
#296: FILE: drivers/crypto/qat/qat_sym_session.c:2017:
+ if (session->qat_dir == ICP_QAT_HW_CIPHER_DECRYPT) {
[...]
+ } else {
[...]
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#297: FILE: drivers/crypto/qat/qat_sym_session.c:2018:
+ ICP_QAT_FW_SYM_DIR_FLAG_SET(header->serv_specif_flags, ICP_QAT_HW_CIPHER_DECRYPT);
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#299: FILE: drivers/crypto/qat/qat_sym_session.c:2020:
+ ICP_QAT_FW_SYM_DIR_FLAG_SET(header->serv_specif_flags, ICP_QAT_HW_CIPHER_ENCRYPT);
total: 0 errors, 6 warnings, 206 lines checked
parent reply other threads:[~2024-02-29 18:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240229184347.2496000-3-ciara.power@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=20240229184421.3C07F12232A@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ciara.power@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).