automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kai Ji <kai.ji@intel.com>
Subject: |WARNING| pw106673 [dpdk-dev v5 03/10] crypto/qat: qat generation specific enqueue
Date: Fri, 28 Jan 2022 19:24:26 +0100 (CET)	[thread overview]
Message-ID: <20220128182426.7A3B2120933@dpdk.org> (raw)
In-Reply-To: <20220128182314.23471-4-kai.ji@intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/106673

_coding style issues_


WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#97: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c:156:
+			(void *)&req->serv_specif_rqpars;

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#102: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c:161:
+		cipher_param = (void *)&req->serv_specif_rqpars;

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#140: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c:199:
+	cipher_param = (void *)&req->serv_specif_rqpars;

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#195: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c:254:
+			req->comn_hdr.serv_specif_flags,

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#198: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c:257:
+			req->comn_hdr.serv_specif_flags,

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#230: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c:116:
+			(void *)&req->serv_specif_rqpars;

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#232: FILE: drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c:118:
+			(void *)&req->serv_specif_rqpars;

total: 0 errors, 7 warnings, 171 lines checked

           reply	other threads:[~2022-01-28 18:24 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20220128182314.23471-4-kai.ji@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=20220128182426.7A3B2120933@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=kai.ji@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).