automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-test-report] |WARNING| pw93630 [PATCH 07/15] crypto/qat: rework init common header function
Date: Mon, 31 May 2021 16:12:01 +0200 (CEST)	[thread overview]
Message-ID: <20210531141201.E5827122E1E@dpdk.org> (raw)
In-Reply-To: <20210531141027.13289-8-arkadiuszx.kusztal@intel.com>

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

_coding style issues_


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

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

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#432: FILE: drivers/crypto/qat/qat_sym_session.c:1515:
+			ICP_QAT_FW_LA_RET_AUTH_SET(header->serv_specif_flags,

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#434: FILE: drivers/crypto/qat/qat_sym_session.c:1517:
+			ICP_QAT_FW_LA_CMP_AUTH_SET(header->serv_specif_flags,

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#437: FILE: drivers/crypto/qat/qat_sym_session.c:1520:
+			ICP_QAT_FW_LA_RET_AUTH_SET(header->serv_specif_flags,

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#439: FILE: drivers/crypto/qat/qat_sym_session.c:1522:
+			ICP_QAT_FW_LA_CMP_AUTH_SET(header->serv_specif_flags,

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#443: FILE: drivers/crypto/qat/qat_sym_session.c:1526:
+		ICP_QAT_FW_LA_RET_AUTH_SET(header->serv_specif_flags,

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#445: FILE: drivers/crypto/qat/qat_sym_session.c:1528:
+		ICP_QAT_FW_LA_CMP_AUTH_SET(header->serv_specif_flags,

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

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#463: FILE: drivers/crypto/qat/qat_sym_session.c:1538:
+	ICP_QAT_FW_LA_UPDATE_STATE_SET(header->serv_specif_flags,

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#465: FILE: drivers/crypto/qat/qat_sym_session.c:1540:
+	ICP_QAT_FW_LA_DIGEST_IN_BUFFER_SET(header->serv_specif_flags,

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#478: FILE: drivers/crypto/qat/qat_sym_session.c:1559:
+			&cdesc->fw_req.serv_specif_rqpars;

WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#481: FILE: drivers/crypto/qat/qat_sym_session.c:1562:
+			&cdesc->fw_req.serv_specif_rqpars;

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (16, 32)
#495: FILE: drivers/crypto/qat/qat_sym_session.c:1603:
+		if (cdesc->qat_cipher_alg ==
[...]
+				cdesc->qat_dir = ICP_QAT_HW_CIPHER_DECRYPT;

total: 0 errors, 14 warnings, 607 lines checked

           reply	other threads:[~2021-05-31 14:12 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210531141027.13289-8-arkadiuszx.kusztal@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=20210531141201.E5827122E1E@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=arkadiuszx.kusztal@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).