From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tejasree Kondoj <ktejasree@marvell.com>
Subject: |WARNING| pw126630 [PATCH 3/7] crypto/cnxk: add CN10K pdcp chain support
Date: Fri, 28 Apr 2023 16:48:07 +0200 (CEST) [thread overview]
Message-ID: <20230428144807.8E4F9120698@dpdk.org> (raw)
In-Reply-To: <20230428144647.1072-4-ktejasree@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/126630
_coding style issues_
WARNING:TYPO_SPELLING: 'ciph' may be misspelled - perhaps 'cipher'?
#97: FILE: drivers/common/cnxk/roc_se.c:55:
+cpt_ciph_type_set(roc_se_cipher_type type, struct roc_se_ctx *ctx, uint16_t key_len)
WARNING:TYPO_SPELLING: 'ciph' may be misspelled - perhaps 'cipher'?
#99: FILE: drivers/common/cnxk/roc_se.c:57:
+ bool chained_op = ctx->ciph_then_auth || ctx->auth_then_ciph;
WARNING:TYPO_SPELLING: 'ciph' may be misspelled - perhaps 'cipher'?
#99: FILE: drivers/common/cnxk/roc_se.c:57:
+ bool chained_op = ctx->ciph_then_auth || ctx->auth_then_ciph;
WARNING:TYPO_SPELLING: 'ciph' may be misspelled - perhaps 'cipher'?
#159: FILE: drivers/common/cnxk/roc_se.c:461:
+ opcode_minor = se_ctx->ciph_then_auth ? 2 : 3;
WARNING:TYPO_SPELLING: 'ciph' may be misspelled - perhaps 'cipher'?
#180: FILE: drivers/common/cnxk/roc_se.c:712:
+ se_ctx->template_w4.s.opcode_minor = se_ctx->ciph_then_auth ? 2 : 3;
WARNING:TYPO_SPELLING: 'ciph' may be misspelled - perhaps 'cipher'?
#331: FILE: drivers/crypto/cnxk/cnxk_se.h:883:
+ if (cpt_ctx->ciph_then_auth && (req_flags & ROC_SE_VALID_MAC_BUF))
WARNING:TYPO_SPELLING: 'ciph' may be misspelled - perhaps 'cipher'?
#433: FILE: drivers/crypto/cnxk/cnxk_se.h:985:
+ if (cpt_ctx->ciph_then_auth && (req_flags & ROC_SE_VALID_MAC_BUF))
total: 0 errors, 7 warnings, 545 lines checked
parent reply other threads:[~2023-04-28 14:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230428144647.1072-4-ktejasree@marvell.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=20230428144807.8E4F9120698@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ktejasree@marvell.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).