automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gagandeep Singh <g.singh@nxp.com>
Subject: [dpdk-test-report] |WARNING| pw76671 [PATCH 4/7] raw/dpaa2_qdma: optimize IOVA conversion
Date: Wed,  9 Sep 2020 01:47:12 +0200 (CEST)	[thread overview]
Message-ID: <20200908234712.B3B6E1BEB1@dpdk.org> (raw)
In-Reply-To: <1599470764-30569-5-git-send-email-g.singh@nxp.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#78: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:226:
+	uint64_t elem_iova, fle_iova;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#87: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:234:
+	ret = rte_mempool_get(qdma_dev->fle_pool, (void **)(&elem));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#102: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:249:
+			((uint64_t)elem + QDMA_FLE_JOB_OFFSET);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#106: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:252:
+	fle = (struct qbman_fle *)

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#106: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:252:
+	fle = (struct qbman_fle *)

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#107: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:253:
+			((uint64_t)elem + QDMA_FLE_FLE_OFFSET);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#108: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:254:
+	fle_iova = elem_iova + QDMA_FLE_FLE_OFFSET;

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#108: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:254:
+	fle_iova = elem_iova + QDMA_FLE_FLE_OFFSET;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#111: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:256:
+	DPAA2_SET_FD_ADDR(fd, fle_iova);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#120: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:299:
+	struct qbman_fle *fle;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#120: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:299:
+	struct qbman_fle *fle;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#129: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:308:
+	fle = (struct qbman_fle *)

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#129: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:308:
+	fle = (struct qbman_fle *)

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#132: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:310:
+	elem = (void *)((uint64_t)fle - QDMA_FLE_FLE_OFFSET);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#132: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:310:
+	elem = (void *)((uint64_t)fle - QDMA_FLE_FLE_OFFSET);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#135: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:313:
+			((uint64_t)elem + QDMA_FLE_JOB_OFFSET);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#144: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:321:
+	rte_mempool_put(qdma_dev->fle_pool, elem);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#157: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.h:21:
+#define QDMA_FLE_JOB_OFFSET 0

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#158: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.h:22:
+#define QDMA_FLE_FLE_OFFSET \

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#159: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.h:23:
+		(QDMA_FLE_JOB_OFFSET + sizeof(struct rte_qdma_job *))

total: 0 errors, 20 warnings, 82 lines checked

           reply	other threads:[~2020-09-08 23:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1599470764-30569-5-git-send-email-g.singh@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=20200908234712.B3B6E1BEB1@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=g.singh@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).