From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gagandeep Singh <g.singh@nxp.com>
Subject: |WARNING| pw145402 [v5 04/15] dma/dpaa2: add short FD support
Date: Tue, 8 Oct 2024 13:01:00 +0200 (CEST) [thread overview]
Message-ID: <20241008110100.E4A5B120757@dpdk.org> (raw)
In-Reply-To: <20241008105810.1454133-5-g.singh@nxp.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/145402
_coding style issues_
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#104:
performance than FLE.
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#105:
1) Save index context in FD att field for short and FLE(NonSG).
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#107:
3) Force 48 bits address for source address and fle according to spec.
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#152: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:586:
+ } else if (fle[DPAA2_QDMA_SRC_FLE].word4.fmt !=
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#152: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:586:
+ } else if (fle[DPAA2_QDMA_SRC_FLE].word4.fmt !=
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#186: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:679:
+ dpaa2_qdma_fd_set_addr(fd, fle_iova);
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#205: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:735:
+ struct dpaa2_qdma_rbp *rbp, int ser)
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#215: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:745:
+ fd->simple_pci.ser = ser;
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#215: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:745:
+ fd->simple_pci.ser = ser;
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#216: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:746:
+ if (ser)
WARNING:TYPO_SPELLING: 'SER' may be misspelled - perhaps 'SET'?
#217: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:747:
+ fd->simple.frc |= QDMA_SER_CTX;
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#248: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:778:
+ uint32_t len, struct qbman_fd *fd, int ser)
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#258: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:788:
+ fd->simple_ddr.ser = ser;
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#258: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:788:
+ fd->simple_ddr.ser = ser;
WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#259: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:789:
+ if (ser)
WARNING:TYPO_SPELLING: 'SER' may be misspelled - perhaps 'SET'?
#260: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:790:
+ fd->simple.frc |= QDMA_SER_CTX;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#337: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:859:
+ struct qdma_cntx_fle_sdd *fle_sdd = NULL;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#337: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:859:
+ struct qdma_cntx_fle_sdd *fle_sdd = NULL;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#338: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:860:
+ rte_iova_t fle_iova, sdd_iova;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#347: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:867:
+ fle_sdd = qdma_vq->cntx_fle_sdd[qdma_vq->silent_idx];
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#347: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:867:
+ fle_sdd = qdma_vq->cntx_fle_sdd[qdma_vq->silent_idx];
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#351: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:870:
+ (void **)&fle_sdd);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#363: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:876:
+ fle = fle_sdd->fle;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#363: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:876:
+ fle = fle_sdd->fle;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#363: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:876:
+ fle = fle_sdd->fle;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#364: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:877:
+ fle_iova = (uint64_t)fle - qdma_vq->fle_iova2va_offset;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#364: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:877:
+ fle_iova = (uint64_t)fle - qdma_vq->fle_iova2va_offset;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#364: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:877:
+ fle_iova = (uint64_t)fle - qdma_vq->fle_iova2va_offset;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#372: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:879:
+ dpaa2_qdma_fd_set_addr(fd, fle_iova);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#375: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:881:
+ DPAA2_SET_FD_FLC(fd, (uint64_t)fle);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#380: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:885:
+ fle_sdd_pre_populate(fle_sdd,
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#380: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:885:
+ fle_sdd_pre_populate(fle_sdd,
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#395: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:892:
+ sdd = fle_sdd->sdd;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#396: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:893:
+ sdd_iova = (uint64_t)sdd - qdma_vq->fle_iova2va_offset;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#404: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:900:
+ dpaa2_qdma_long_fmt_dump(fle);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#450: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:943:
+ uint16_t *free_space, uint16_t *fle_elem_nb)
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#456: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:949:
+ struct qdma_cntx_fle_sdd *fle_sdd;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#456: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:949:
+ struct qdma_cntx_fle_sdd *fle_sdd;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#471: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:964:
+ fle_sdd = (void *)(uintptr_t)DPAA2_GET_FD_FLC(fd);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#472: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:965:
+ qdma_vq->fle_elem[*fle_elem_nb] = fle_sdd;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#472: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:965:
+ qdma_vq->fle_elem[*fle_elem_nb] = fle_sdd;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#472: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:965:
+ qdma_vq->fle_elem[*fle_elem_nb] = fle_sdd;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#473: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:966:
+ (*fle_elem_nb)++;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#482: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:975:
+ fle_sdd = (void *)(uintptr_t)DPAA2_GET_FD_FLC(fd);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#483: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:976:
+ qdma_vq->fle_elem[*fle_elem_nb] = fle_sdd;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#483: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:976:
+ qdma_vq->fle_elem[*fle_elem_nb] = fle_sdd;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#483: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:976:
+ qdma_vq->fle_elem[*fle_elem_nb] = fle_sdd;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#484: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:977:
+ (*fle_elem_nb)++;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#485: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:978:
+ cntx_sg = container_of(fle_sdd,
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#486: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:979:
+ struct qdma_cntx_sg, fle_sdd);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#538: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1111:
+ ret = dpaa2_qdma_dq_fd(fd, qdma_vq, &free_space, &fle_elem_nb);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#549: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1137:
+ if (fle_elem_nb > 0) {
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#550: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1138:
+ rte_mempool_put_bulk(qdma_vq->fle_pool,
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#551: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1139:
+ qdma_vq->fle_elem, fle_elem_nb);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#551: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1139:
+ qdma_vq->fle_elem, fle_elem_nb);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#579: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1396:
+ (void **)qdma_dev->vqs[vchan].cntx_fle_sdd,
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#706: FILE: drivers/dma/dpaa2/dpaa2_qdma.h:268:
+ uint64_t fle_iova2va_offset;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#723: FILE: drivers/dma/dpaa2/dpaa2_qdma.h:290:
+ struct qdma_cntx_fle_sdd *cntx_fle_sdd[DPAA2_QDMA_MAX_DESC];
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#723: FILE: drivers/dma/dpaa2/dpaa2_qdma.h:290:
+ struct qdma_cntx_fle_sdd *cntx_fle_sdd[DPAA2_QDMA_MAX_DESC];
total: 0 errors, 59 warnings, 596 lines checked
parent reply other threads:[~2024-10-08 11:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20241008105810.1454133-5-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=20241008110100.E4A5B120757@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).