[dpdk-test-report] |WARNING| pw98131 [PATCH v2 06/15] crypto/dpaa2_sec: support AUTH only with raw buffer APIs

automatic DPDK test reports
 help / color / mirror / Atom feed

From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: [dpdk-test-report] |WARNING| pw98131 [PATCH v2 06/15] crypto/dpaa2_sec: support AUTH only with raw buffer APIs
Date: Tue,  7 Sep 2021 10:05:01 +0200 (CEST)	[thread overview]
Message-ID: <20210907080501.8A79D122D3F@dpdk.org> (raw)
In-Reply-To: <20210907075957.28848-7-hemant.agrawal@nxp.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#182: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:83:
+	struct qbman_fle *fle, *sge, *ip_fle, *op_fle;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#182: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:83:
+	struct qbman_fle *fle, *sge, *ip_fle, *op_fle;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#182: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:83:
+	struct qbman_fle *fle, *sge, *ip_fle, *op_fle;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#182: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:83:
+	struct qbman_fle *fle, *sge, *ip_fle, *op_fle;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#205: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:106:
+	fle = (struct qbman_fle *)rte_malloc(NULL,

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#205: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:106:
+	fle = (struct qbman_fle *)rte_malloc(NULL,

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#206: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:107:
+		FLE_SG_MEM_SIZE(2 * sgl->num),

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#208: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:109:
+	if (unlikely(!fle)) {

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#212: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:113:
+	memset(fle, 0, FLE_SG_MEM_SIZE(2*sgl->num));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#212: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:113:
+	memset(fle, 0, FLE_SG_MEM_SIZE(2*sgl->num));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#213: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:114:
+	/* first FLE entry used to store mbuf and session ctxt */

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#214: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:115:
+	DPAA2_SET_FLE_ADDR(fle, (size_t)userdata);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#214: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:115:
+	DPAA2_SET_FLE_ADDR(fle, (size_t)userdata);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#215: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:116:
+	DPAA2_FLE_SAVE_CTXT(fle, (ptrdiff_t)priv);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#215: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:116:
+	DPAA2_FLE_SAVE_CTXT(fle, (ptrdiff_t)priv);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#216: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:117:
+	op_fle = fle + 1;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#216: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:117:
+	op_fle = fle + 1;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#217: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:118:
+	ip_fle = fle + 2;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#217: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:118:
+	ip_fle = fle + 2;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#218: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:119:
+	sge = fle + 3;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#224: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:125:
+	DPAA2_SET_FD_ADDR(fd, DPAA2_VADDR_TO_IOVA(op_fle));

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#227: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:128:
+	/* o/p fle */

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#228: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:129:
+	DPAA2_SET_FLE_ADDR(op_fle,

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#228: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:129:
+	DPAA2_SET_FLE_ADDR(op_fle,

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#230: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:131:
+	op_fle->length = sess->digest_length;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#232: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:133:
+	/* i/p fle */

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#233: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:134:
+	DPAA2_SET_FLE_SG_EXT(ip_fle);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#233: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:134:
+	DPAA2_SET_FLE_SG_EXT(ip_fle);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#234: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:135:
+	DPAA2_SET_FLE_ADDR(ip_fle, DPAA2_VADDR_TO_IOVA(sge));

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#234: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:135:
+	DPAA2_SET_FLE_ADDR(ip_fle, DPAA2_VADDR_TO_IOVA(sge));

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#235: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:136:
+	ip_fle->length = data_len;

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#252: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:153:
+		DPAA2_SET_FLE_ADDR(sge, DPAA2_VADDR_TO_IOVA(iv_ptr));

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#253: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:154:
+		ip_fle->length += sge->length;

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#257: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:158:
+	DPAA2_SET_FLE_ADDR(sge, sgl->vec[0].iova);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#258: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:159:
+	DPAA2_SET_FLE_OFFSET(sge, data_offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#267: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:168:
+			DPAA2_SET_FLE_ADDR(sge, sgl->vec[i].iova);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#268: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:169:
+			DPAA2_SET_FLE_OFFSET(sge, 0);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#278: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:179:
+		DPAA2_SET_FLE_ADDR(sge, DPAA2_VADDR_TO_IOVA(old_digest));

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#280: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:181:
+		ip_fle->length += sess->digest_length;

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#282: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:183:
+	DPAA2_SET_FLE_FIN(sge);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#283: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:184:
+	DPAA2_SET_FLE_FIN(ip_fle);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#283: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:184:
+	DPAA2_SET_FLE_FIN(ip_fle);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#284: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:185:
+	DPAA2_SET_FD_LEN(fd, ip_fle->length);

total: 0 errors, 43 warnings, 155 lines checked

          parent reply	other threads:[~2021-09-07  8:05 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210907075957.28848-7-hemant.agrawal@nxp.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=20210907080501.8A79D122D3F@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=hemant.agrawal@nxp.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).