From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gagandeep Singh <g.singh@nxp.com>
Subject: [dpdk-test-report] |WARNING| pw80852 [PATCH v2 7/7] raw/dpaa2_qdma: support enqueue without response wait
Date: Thu, 15 Oct 2020 11:50:32 +0200 (CEST) [thread overview]
Message-ID: <20201015095032.38E9D1DE0D@dpdk.org> (raw)
In-Reply-To: <1602755228-25535-8-git-send-email-g.singh@nxp.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/80852
_coding style issues_
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#64:
qDMA FLE pool is not used in this condition since there is no chance to put
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#65:
FLE back to pool without dequeue response.
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#67:
User application is responsible to transfer FLE memory to qDMA driver
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#85: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:49:
+ struct rte_qdma_rbp *rbp, int ser)
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#94: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:59:
+ fd->simple_pci.ser = ser;
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#94: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:59:
+ fd->simple_pci.ser = ser;
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#103: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:84:
+ uint32_t len, struct qbman_fd *fd, int ser)
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#112: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:94:
+ fd->simple_ddr.ser = ser;
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#112: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:94:
+ fd->simple_ddr.ser = ser;
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#120: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:207:
+ int ser = (qdma_vq->flags & RTE_QDMA_VQ_NO_RESPONSE) ?
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#132: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:224:
+ job[loop]->len, &fd[loop], rbp, ser);
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#138: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:228:
+ job[loop]->len, &fd[loop], ser);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#156: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:305:
+ struct qbman_fle *fle;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#156: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:305:
+ struct qbman_fle *fle;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#157: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:306:
+ uint64_t elem_iova, fle_iova;
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#169: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:318:
+ QDMA_FLE_SINGLE_JOB_OFFSET);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#174: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:323:
+ fle = (struct qbman_fle *)
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#174: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:323:
+ fle = (struct qbman_fle *)
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#175: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:324:
+ ((uintptr_t)(uint64_t)elem + QDMA_FLE_FLE_OFFSET);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#176: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:325:
+ fle_iova = elem_iova + QDMA_FLE_FLE_OFFSET;
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#176: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:325:
+ fle_iova = elem_iova + QDMA_FLE_FLE_OFFSET;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#178: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:327:
+ DPAA2_SET_FD_ADDR(&fd[i], fle_iova);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#181: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:330:
+ memset(fle, 0, DPAA2_QDMA_MAX_FLE * sizeof(struct qbman_fle) +
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#181: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:330:
+ memset(fle, 0, DPAA2_QDMA_MAX_FLE * sizeof(struct qbman_fle) +
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#181: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:330:
+ memset(fle, 0, DPAA2_QDMA_MAX_FLE * sizeof(struct qbman_fle) +
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#184: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:333:
+ dpaa2_qdma_populate_fle(fle, fle_iova, rbp,
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#184: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:333:
+ dpaa2_qdma_populate_fle(fle, fle_iova, rbp,
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#184: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:333:
+ dpaa2_qdma_populate_fle(fle, fle_iova, rbp,
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#186: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:335:
+ job[i]->flags, QBMAN_FLE_WORD4_FMT_SBF);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#206: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:416:
+ ret = rte_mempool_get(qdma_vq->fle_pool, &elem);
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#208: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:418:
+ DPAA2_QDMA_DP_DEBUG("Memory alloc failed for FLE");
WARNING:TYPO_SPELLING: 'SER' may be misspelled - perhaps 'SET'?
#220: FILE: drivers/raw/dpaa2_qdma/dpaa2_qdma.c:447:
+ DPAA2_SET_FD_FRC(fd, QDMA_SER_CTX);
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#256: FILE: drivers/raw/dpaa2_qdma/rte_pmd_dpaa2_qdma.h:160:
+ * FLE pool element maintained by user, in case no qDMA response.
total: 0 errors, 33 warnings, 167 lines checked
next parent reply other threads:[~2020-10-15 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1602755228-25535-8-git-send-email-g.singh@nxp.com>
2020-10-15 9:50 ` checkpatch [this message]
2020-10-15 13:56 ` [dpdk-test-report] |WARNING| pw80852 " 0-day Robot
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=20201015095032.38E9D1DE0D@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).