From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5D984430DE for ; Wed, 23 Aug 2023 09:11:11 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 568F640A79; Wed, 23 Aug 2023 09:11:11 +0200 (CEST) Received: from dpdk.org (dpdk.org [92.243.24.197]) by mails.dpdk.org (Postfix) with ESMTP id 1B88440ED6 for ; Wed, 23 Aug 2023 09:10:51 +0200 (CEST) Received: by dpdk.org (Postfix, from userid 65534) id 18F051206AB; Wed, 23 Aug 2023 09:10:51 +0200 (CEST) Subject: |WARNING| pw130669 [PATCH 07/12] crypto/dpaa2_sec: enhance dpaa FD FL FMT offset set In-Reply-To: <20230823070855.27532-8-hemant.agrawal@nxp.com> References: <20230823070855.27532-8-hemant.agrawal@nxp.com> To: test-report@dpdk.org From: checkpatch@dpdk.org Cc: Hemant Agrawal Message-Id: <20230823071051.18F051206AB@dpdk.org> Date: Wed, 23 Aug 2023 09:10:51 +0200 (CEST) X-BeenThere: test-report@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: automatic DPDK test reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: test-report-bounces@dpdk.org Test-Label: checkpatch Test-Status: WARNING http://dpdk.org/patch/130669 _coding style issues_ WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'? #101: The macro DPAA2_SET_FLE_OFFSET(fle, offset) only works for masking the WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'? #101: The macro DPAA2_SET_FLE_OFFSET(fle, offset) only works for masking the WARNING:TYPO_SPELLING: 'upto' may be misspelled - perhaps 'up to'? #102: offset upto with 12 bits. When the offset value is more that 12 bits, WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'? #105: The FLE_ADDR is modified to FLE_ADDR + OFFSET, and the FLE_OFFSET WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'? #105: The FLE_ADDR is modified to FLE_ADDR + OFFSET, and the FLE_OFFSET WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'? #105: The FLE_ADDR is modified to FLE_ADDR + OFFSET, and the FLE_OFFSET WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'? #125: 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'? #134: 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'? #144: 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'? #154: 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'? #164: 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'? #164: 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'? #170: 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'? #170: 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'? #180: 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'? #189: 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'? #200: 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'? #209: 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'? #219: 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'? #230: 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'? #240: 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'? #249: 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'? #260: 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'? #269: 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'? #280: 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'? #291: 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'? #301: 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'? #311: 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'? #321: 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'? #331: 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'? #340: 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'? #356: 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'? #365: 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'? #375: 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'? #375: 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'? #385: 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'? #399: 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'? #414: 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'? #431: 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'? #447: 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'? #461: 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'? #478: 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'? #495: 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'? #558: 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'? #572: 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'? #595: 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'? #616: 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