[dpdk-test-report] |WARNING| pw101490 [PATCH v4 05/15] crypto/dpaa2_sec: support raw datapath 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| pw101490 [PATCH v4 05/15] crypto/dpaa2_sec: support raw datapath APIs
Date: Wed, 13 Oct 2021 21:06:22 +0200 (CEST)	[thread overview]
Message-ID: <20211013190622.F2962121D26@dpdk.org> (raw)
In-Reply-To: <20211013190032.2308-6-hemant.agrawal@nxp.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#188: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h:20:
+/* FLE_POOL_NUM_BUFS is set as per the ipsec-secgw application */

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#189: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h:21:
+#define FLE_POOL_NUM_BUFS	32000

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#190: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h:22:
+#define FLE_POOL_BUF_SIZE	256

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#191: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h:23:
+#define FLE_POOL_CACHE_SIZE	512

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#192: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h:24:
+#define FLE_SG_MEM_SIZE(num)	(FLE_POOL_BUF_SIZE + ((num) * 32))

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#192: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h:24:
+#define FLE_SG_MEM_SIZE(num)	(FLE_POOL_BUF_SIZE + ((num) * 32))

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#495: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:215:
+		"RAW CIPHER SG: 1 - flc = %p, fle = %p FLEaddr = %x-%x, len %d
",

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#496: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:216:
+		flc, fle, fle->addr_hi, fle->addr_lo,

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#496: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:216:
+		flc, fle, fle->addr_hi, fle->addr_lo,

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#496: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:216:
+		flc, fle, fle->addr_hi, fle->addr_lo,

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#497: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:217:
+		fle->length);

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

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

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

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

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

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#506: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:226:
+	DPAA2_SET_FLE_ADDR(sge, iv->iova);

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

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

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

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

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

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

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

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

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

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

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#662: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:382:
+	struct qbman_fle *fle;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#662: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:382:
+	struct qbman_fle *fle;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#664: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:384:
+	fle = (struct qbman_fle *)DPAA2_IOVA_TO_VADDR(DPAA2_GET_FD_ADDR(fd));

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#664: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:384:
+	fle = (struct qbman_fle *)DPAA2_IOVA_TO_VADDR(DPAA2_GET_FD_ADDR(fd));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#666: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:386:
+	DPAA2_SEC_DP_DEBUG("FLE addr = %x - %x, offset = %x
",

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#667: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:387:
+			   fle->addr_hi, fle->addr_lo, fle->fin_bpid_offset);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#667: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:387:
+			   fle->addr_hi, fle->addr_lo, fle->fin_bpid_offset);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#667: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:387:
+			   fle->addr_hi, fle->addr_lo, fle->fin_bpid_offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#668: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:388:
+	userdata = (struct rte_crypto_op *)DPAA2_GET_FLE_ADDR((fle - 1));

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#668: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:388:
+	userdata = (struct rte_crypto_op *)DPAA2_GET_FLE_ADDR((fle - 1));

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#669: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:389:
+	/* free the fle memory */

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#670: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:390:
+	rte_free((void *)(fle-1));

total: 0 errors, 72 warnings, 735 lines checked

          parent reply	other threads:[~2021-10-13 19:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20211013190032.2308-6-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=20211013190622.F2962121D26@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).