[dpdk-test-report] |WARNING| pw98134 [PATCH v2 09/15] crypto/dpaa2_sec: support OOP with raw buffer API

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: [dpdk-test-report] |WARNING| pw98134 [PATCH v2 09/15] crypto/dpaa2_sec: support OOP with raw buffer API
Date: Tue,  7 Sep 2021 10:06:50 +0200 (CEST)	[thread overview]
Message-ID: <20210907080650.88C18122D3F@dpdk.org> (raw)
In-Reply-To: <20210907075957.28848-10-hemant.agrawal@nxp.com>

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

_coding style issues_


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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#158: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:97:
+		DPAA2_SET_FLE_OFFSET(sge, ofs.ofs.cipher.head);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#171: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:104:
+			DPAA2_SET_FLE_OFFSET(sge, 0);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#177: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:110:
+		DPAA2_SET_FLE_OFFSET(sge, ofs.ofs.cipher.head);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#184: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:117:
+			DPAA2_SET_FLE_OFFSET(sge, 0);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#210: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:244:
+		DPAA2_SET_FLE_OFFSET(sge, ofs.ofs.cipher.head);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#223: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:251:
+			DPAA2_SET_FLE_OFFSET(sge, 0);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#229: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:257:
+		DPAA2_SET_FLE_OFFSET(sge, ofs.ofs.cipher.head);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#236: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:264:
+			DPAA2_SET_FLE_OFFSET(sge, 0);

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

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#291: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:517:
+			DPAA2_SET_FLE_OFFSET(sge, 0);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#300: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:526:
+		DPAA2_SET_FLE_OFFSET(sge, 0);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#307: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:533:
+			DPAA2_SET_FLE_OFFSET(sge, 0);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#337: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:657:
+		DPAA2_SET_FLE_OFFSET(sge, data_offset);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#350: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:664:
+			DPAA2_SET_FLE_OFFSET(sge, 0);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#356: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:670:
+		DPAA2_SET_FLE_OFFSET(sge, data_offset);

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

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#363: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:677:
+			DPAA2_SET_FLE_OFFSET(sge, 0);

total: 0 errors, 31 warnings, 235 lines checked

          parent reply	other threads:[~2021-09-07  8:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210907075957.28848-10-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=20210907080650.88C18122D3F@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).