From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: nipun.gupta@nxp.com
Subject: |WARNING| pw110660 [PATCH v2 3/6] dma/dpaa2: support basic operations
Date: Thu, 5 May 2022 09:32:43 +0200 (CEST) [thread overview]
Message-ID: <20220505073243.AFC9D124164@dpdk.org> (raw)
In-Reply-To: <20220505073108.17112-4-nipun.gupta@nxp.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/110660
_coding style issues_
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#173: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:111:
+ pool_size = QDMA_FLE_SG_POOL_SIZE;
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#175: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:113:
+ pool_size = QDMA_FLE_SINGLE_POOL_SIZE;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#193: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:131:
+ "qdma_fle_pool_dev%d_qid%d", dpdmai_dev->dpdmai_id, vchan);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#194: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:132:
+ qdma_dev->vqs[vchan].fle_pool = rte_mempool_create(pool_name,
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#196: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:134:
+ QDMA_FLE_CACHE_SIZE(conf->nb_desc), 0,
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#198: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:136:
+ if (!qdma_dev->vqs[vchan].fle_pool) {
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#199: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:137:
+ DPAA2_QDMA_ERR("qdma_fle_pool create failed");
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#207: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:145:
+ QDMA_FLE_CACHE_SIZE(conf->nb_desc), 0,
total: 0 errors, 8 warnings, 201 lines checked
parent reply other threads:[~2022-05-05 7:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220505073108.17112-4-nipun.gupta@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=20220505073243.AFC9D124164@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=nipun.gupta@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).