|WARNING| pw131741 [PATCH v2 07/13] crypto/dpaa2_sec: enhance dpaa FD FL FMT offset set

automatic DPDK test reports
 help / color / mirror / Atom feed

From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: |WARNING| pw131741 [PATCH v2 07/13] crypto/dpaa2_sec: enhance dpaa FD FL FMT offset set
Date: Wed, 20 Sep 2023 15:38:02 +0200 (CEST)	[thread overview]
Message-ID: <20230920133802.500C9120802@dpdk.org> (raw)
In-Reply-To: <20230920133403.6420-8-hemant.agrawal@nxp.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#102: 
The macro DPAA2_SET_FLE_OFFSET(fle, offset) only works for masking the

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#102: 
The macro DPAA2_SET_FLE_OFFSET(fle, offset) only works for masking the

WARNING:TYPO_SPELLING: 'upto' may be misspelled - perhaps 'up to'?
#103: 
offset upto with 12 bits. When the offset value is more that 12 bits,

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#106: 
The FLE_ADDR is modified to FLE_ADDR + OFFSET, and the FLE_OFFSET

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#106: 
The FLE_ADDR is modified to FLE_ADDR + OFFSET, and the FLE_OFFSET

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#106: 
The FLE_ADDR is modified to FLE_ADDR + OFFSET, and the FLE_OFFSET

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#126: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:141:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#135: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:148:
+		DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#145: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:166:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#155: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:174:
+		DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#165: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:246:
+	DPAA2_SET_FLE_ADDR(op_fle, rte_pktmbuf_iova(dst_mbuf));

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#165: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:246:
+	DPAA2_SET_FLE_ADDR(op_fle, rte_pktmbuf_iova(dst_mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#171: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:250:
+	DPAA2_SET_FLE_ADDR(ip_fle, rte_pktmbuf_iova(src_mbuf));

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#171: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:250:
+	DPAA2_SET_FLE_ADDR(ip_fle, rte_pktmbuf_iova(src_mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#181: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:370:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf) + sym_op->aead.data.offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#190: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:377:
+		DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#201: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:415:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf) + sym_op->aead.data.offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#210: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:422:
+		DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#220: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:527:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(dst) + sym_op->aead.data.offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#231: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:562:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(sym_op->m_src) + sym_op->aead.data.offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#241: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:655:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf) + sym_op->auth.data.offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#250: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:662:
+		DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#261: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:693:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf) + sym_op->auth.data.offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#270: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:700:
+		DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#281: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:814:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(dst) + sym_op->cipher.data.offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#292: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:844:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(sym_op->m_src) + sym_op->auth.data.offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#302: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:945:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf) + data_offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#312: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:957:
+			DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#322: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1075:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(sym_op->m_src) + data_offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#332: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1160:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf) + data_offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#341: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1167:
+		DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#357: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1192:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf) + data_offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#366: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1199:
+		DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(mbuf));

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#376: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1300:
+	DPAA2_SET_FLE_ADDR(fle, rte_pktmbuf_iova(dst) + data_offset);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#376: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1300:
+	DPAA2_SET_FLE_ADDR(fle, rte_pktmbuf_iova(dst) + data_offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#386: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1320:
+	DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(sym_op->m_src) + data_offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#400: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:98:
+		DPAA2_SET_FLE_ADDR(sge, dest_sgl->vec[0].iova + ofs.ofs.cipher.head);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#415: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:110:
+		DPAA2_SET_FLE_ADDR(sge, sgl->vec[0].iova + ofs.ofs.cipher.head);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#432: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:147:
+	DPAA2_SET_FLE_ADDR(sge, sgl->vec[0].iova + ofs.ofs.auth.head);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#448: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:241:
+		DPAA2_SET_FLE_ADDR(sge, dest_sgl->vec[0].iova +  ofs.ofs.cipher.head);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#462: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:252:
+		DPAA2_SET_FLE_ADDR(sge, sgl->vec[0].iova + ofs.ofs.cipher.head);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#479: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:292:
+	DPAA2_SET_FLE_ADDR(sge, sgl->vec[0].iova + ofs.ofs.cipher.head);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#496: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:403:
+	DPAA2_SET_FLE_ADDR(sge, sgl->vec[0].iova + data_offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#559: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:621:
+		DPAA2_SET_FLE_ADDR(sge, dest_sgl->vec[0].iova + data_offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#573: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:632:
+		DPAA2_SET_FLE_ADDR(sge, sgl->vec[0].iova + data_offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#596: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:662:
+	DPAA2_SET_FLE_ADDR(sge, sgl->vec[0].iova + data_offset);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#617: FILE: drivers/net/dpaa2/dpaa2_rxtx.c:474:
+		DPAA2_SET_FLE_ADDR(sge, rte_pktmbuf_iova(cur_seg));

total: 0 errors, 47 warnings, 0 checks, 462 lines checked

          parent reply	other threads:[~2023-09-20 13:38 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20230920133403.6420-8-hemant.agrawal@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=20230920133802.500C9120802@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=hemant.agrawal@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).