automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Fan Zhang <roy.fan.zhang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw73971 [dpdk-dev v5 2/4] crypto/qat: add support to direct data-path APIs
Date: Mon, 13 Jul 2020 18:59:48 +0200 (CEST)	[thread overview]
Message-ID: <20200713165948.3B5AE1D6B9@dpdk.org> (raw)
In-Reply-To: <20200713165755.61814-3-roy.fan.zhang@intel.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#201: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:64:
+				qat_req->comn_hdr.serv_specif_flags,

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

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#313: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:176:
+				req->comn_hdr.serv_specif_flags,

WARNING:MULTILINE_DEREFERENCE: Avoid multiple line dereference - prefer 'cipher_param->u.cipher_IV_array'
#374: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:237:
+				rte_memcpy(((uint8_t *)cipher_param->
+					u.cipher_IV_array) +

WARNING:MULTILINE_DEREFERENCE: Avoid multiple line dereference - prefer 'cipher_param->u.cipher_IV_array[0]'
#380: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:243:
+				*(uint8_t *)&cipher_param->
+					u.cipher_IV_array[0] =

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

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

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#592: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:455:
+				req->comn_hdr.serv_specif_flags,

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

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#785: FILE: drivers/crypto/qat/qat_sym_hw_dp.c:648:
+					header->serv_specif_flags,

total: 0 errors, 10 warnings, 904 lines checked

           reply	other threads:[~2020-07-13 16:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20200713165755.61814-3-roy.fan.zhang@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=20200713165948.3B5AE1D6B9@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).