From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gagandeep Singh <g.singh@nxp.com>
Subject: |WARNING| pw110067 [PATCH 09/14] crypto/dpaa2_sec: per queue pair fle pool
Date: Fri, 22 Apr 2022 05:54:10 +0200 (CEST) [thread overview]
Message-ID: <20220422035410.BF847120DB4@dpdk.org> (raw)
In-Reply-To: <20220422035100.3180870-9-g.singh@nxp.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/110067
_coding style issues_
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#50:
Subject: [PATCH 09/14] crypto/dpaa2_sec: per queue pair fle pool
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#102:
Driver is creating a fle pool with a fixed number of
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#104:
These fle buffers are equivalent to the number of descriptors.
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#106:
In this patch, creating the fle pool for each queue pair
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#165: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:68:
+free_fle(const struct qbman_fd *fd, struct dpaa2_sec_qp *qp)
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#182: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:81:
+ rte_mempool_put(qp->fle_pool, (void *)(fle-1));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#182: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:81:
+ rte_mempool_put(qp->fle_pool, (void *)(fle-1));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#201: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:224:
+ retval = rte_mempool_get(qp->fle_pool, (void **)(&fle));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#201: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:224:
+ retval = rte_mempool_get(qp->fle_pool, (void **)(&fle));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#237: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:487:
+ retval = rte_mempool_get(qp->fle_pool, (void **)(&fle));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#237: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:487:
+ retval = rte_mempool_get(qp->fle_pool, (void **)(&fle));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#240: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:489:
+ DPAA2_SEC_DP_DEBUG("GCM: no buffer available in fle pool");
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#258: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:779:
+ retval = rte_mempool_get(qp->fle_pool, (void **)(&fle));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#258: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:779:
+ retval = rte_mempool_get(qp->fle_pool, (void **)(&fle));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#261: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:781:
+ DPAA2_SEC_DP_DEBUG("AUTHENC: no buffer available in fle pool");
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#279: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1036:
+ retval = rte_mempool_get(qp->fle_pool, (void **)(&fle));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#279: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1036:
+ retval = rte_mempool_get(qp->fle_pool, (void **)(&fle));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#282: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1038:
+ DPAA2_SEC_DP_DEBUG("AUTH: no buffer available in fle pool");
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#300: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1289:
+ retval = rte_mempool_get(qp->fle_pool, (void **)(&fle));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#300: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1289:
+ retval = rte_mempool_get(qp->fle_pool, (void **)(&fle));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#303: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1291:
+ DPAA2_SEC_DP_DEBUG("CIPHER: no buffer available in fle pool");
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#382: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1542:
+ free_fle(&fd_arr[loop],
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#406: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1656:
+ rte_mempool_put(qp->fle_pool, (void *)(fle-1));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#406: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1656:
+ rte_mempool_put(qp->fle_pool, (void *)(fle-1));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#448: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1889:
+ free_fle(&fd_arr[loop],
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#466: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:2030:
+ rte_mempool_free(qp->fle_pool);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#491: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:2089:
+ snprintf(str, sizeof(str), "sec_fle_pool_p%d_%d_%d",
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#493: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:2091:
+ qp->fle_pool = rte_mempool_create((const char *)str,
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#495: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:2093:
+ FLE_POOL_BUF_SIZE,
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#496: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:2094:
+ FLE_POOL_CACHE_SIZE, 0,
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#499: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:2097:
+ if (!qp->fle_pool) {
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#827: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h:46:
+ struct rte_mempool *fle_pool; /* per device memory pool for FLE */
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#827: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h:46:
+ struct rte_mempool *fle_pool; /* per device memory pool for FLE */
total: 0 errors, 33 warnings, 0 checks, 666 lines checked
parent reply other threads:[~2022-04-22 3:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220422035100.3180870-9-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=20220422035410.BF847120DB4@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).