From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: |WARNING| pw126621 [v1, 3/3] crypto/openssl: add SM2 asymmetric crypto support
Date: Fri, 28 Apr 2023 11:30:15 +0200 (CEST) [thread overview]
Message-ID: <20230428093016.06C5C120698@dpdk.org> (raw)
In-Reply-To: <d0c3d7bb32e29ca56681b80ec46109997f804b19.1682652719.git.gmuthukrishn@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/126621
_coding style issues_
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#147: FILE: drivers/crypto/openssl/openssl_pmd_private.h:206:
+ OSSL_PARAM *key_params;
^
WARNING:TYPO_SPELLING: 'KEYPAIR' may be misspelled - perhaps 'KEY PAIR'?
#194: FILE: drivers/crypto/openssl/rte_openssl_pmd.c:2690:
+ EVP_PKEY_fromdata(kctx, &pkey, EVP_PKEY_KEYPAIR, kparams) <= 0)
WARNING:TYPO_SPELLING: 'KEYPAIR' may be misspelled - perhaps 'KEY PAIR'?
#221: FILE: drivers/crypto/openssl/rte_openssl_pmd.c:2717:
+ || EVP_PKEY_fromdata(kctx, &pkey, EVP_PKEY_KEYPAIR, kparams) <= 0)
WARNING:TYPO_SPELLING: 'KEYPAIR' may be misspelled - perhaps 'KEY PAIR'?
#251: FILE: drivers/crypto/openssl/rte_openssl_pmd.c:2747:
+ EVP_PKEY_fromdata(kctx, &pkey, EVP_PKEY_KEYPAIR, kparams) <= 0)
total: 1 errors, 3 warnings, 425 lines checked
next prev parent reply other threads:[~2023-04-28 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d0c3d7bb32e29ca56681b80ec46109997f804b19.1682652719.git.gmuthukrishn@marvell.com>
2023-04-28 9:17 ` |SUCCESS| pw126619-126621 " qemudev
2023-04-28 9:21 ` qemudev
2023-04-28 9:30 ` checkpatch [this message]
2023-04-28 10:39 ` |SUCCESS| pw126621 " 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=20230428093016.06C5C120698@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=gmuthukrishn@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).