automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chengwen Feng <fengchengwen@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw95646 [PATCH v2] dmadev: introduce DMA device library
Date: Sun, 11 Jul 2021 11:31:08 +0200 (CEST)	[thread overview]
Message-ID: <20210711093108.214EA120F1F@dpdk.org> (raw)
In-Reply-To: <1625995556-41473-1-git-send-email-fengchengwen@huawei.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'multilpe' may be misspelled - perhaps 'multiple'?
#738: FILE: lib/dmadev/rte_dmadev.h:38:
+ * The DMA controller could have multilpe HW-DMA-channels (aka. HW-DMA-queues),

WARNING:MACRO_WITH_FLOW_CONTROL: Macros with flow control statements should be avoided
#850: FILE: lib/dmadev/rte_dmadev.h:150:
+#define RTE_DMADEV_VALID_DEV_ID_OR_ERR_RET(dev_id, retval) do { \
+	if (!rte_dmadev_is_valid_dev(dev_id)) { \
+		RTE_DMADEV_LOG(ERR, "Invalid dev_id=%u
", dev_id); \
+		return retval; \
+	} \
+} while (0)

WARNING:MACRO_WITH_FLOW_CONTROL: Macros with flow control statements should be avoided
#857: FILE: lib/dmadev/rte_dmadev.h:157:
+#define RTE_DMADEV_VALID_DEV_ID_OR_RET(dev_id) do { \
+	if (!rte_dmadev_is_valid_dev(dev_id)) { \
+		RTE_DMADEV_LOG(ERR, "Invalid dev_id=%u
", dev_id); \
+		return; \
+	} \
+} while (0)

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#910: FILE: lib/dmadev/rte_dmadev.h:210:
+/**< DMA device support slave mode & mem-to-dev transfer.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#915: FILE: lib/dmadev/rte_dmadev.h:215:
+/**< DMA device support slave mode & dev-to-mem transfer.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#920: FILE: lib/dmadev/rte_dmadev.h:220:
+/**< DMA device support slave mode & dev-to-dev transfer.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1143: FILE: lib/dmadev/rte_dmadev.h:443:
+/**< DMA transfer direction - slave mode & from memory to device.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1145: FILE: lib/dmadev/rte_dmadev.h:445:
+ * this case, the ARM SoCs works in slave mode, it could initiate a DMA move

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1151: FILE: lib/dmadev/rte_dmadev.h:451:
+/**< DMA transfer direction - slave mode & from device to memory.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1153: FILE: lib/dmadev/rte_dmadev.h:453:
+ * this case, the ARM SoCs works in slave mode, it could initiate a DMA move

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1159: FILE: lib/dmadev/rte_dmadev.h:459:
+/**< DMA transfer direction - slave mode & from device to device.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1161: FILE: lib/dmadev/rte_dmadev.h:461:
+ * this case, the ARM SoCs works in slave mode, it could initiate a DMA move

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1172: FILE: lib/dmadev/rte_dmadev.h:472:
+ * enum rte_dma_slave_port_type - slave mode type defines

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1172: FILE: lib/dmadev/rte_dmadev.h:472:
+ * enum rte_dma_slave_port_type - slave mode type defines

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1174: FILE: lib/dmadev/rte_dmadev.h:474:
+enum rte_dma_slave_port_type {

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1175: FILE: lib/dmadev/rte_dmadev.h:475:
+	/** The slave port is PCIE. */

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#1176: FILE: lib/dmadev/rte_dmadev.h:476:
+	RTE_DMA_SLAVE_PORT_PCIE = 1,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1180: FILE: lib/dmadev/rte_dmadev.h:480:
+ * A structure used to descript slave port parameters.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1182: FILE: lib/dmadev/rte_dmadev.h:482:
+struct rte_dma_slave_port_parameters {

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1183: FILE: lib/dmadev/rte_dmadev.h:483:
+	enum rte_dma_slave_port_type port_type;

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1212: FILE: lib/dmadev/rte_dmadev.h:512:
+	struct rte_dma_slave_port_parameters port;

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1216: FILE: lib/dmadev/rte_dmadev.h:516:
+	struct rte_dma_slave_port_parameters peer_port;

total: 0 errors, 22 warnings, 1893 lines checked
Warning in lib/dmadev/rte_dmadev.c:
Using RTE_LOG_REGISTER, prefer RTE_LOG_REGISTER_(DEFAULT|SUFFIX)

       reply	other threads:[~2021-07-11  9:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1625995556-41473-1-git-send-email-fengchengwen@huawei.com>
2021-07-11  9:31 ` checkpatch [this message]
2021-07-11  9:59 ` [dpdk-test-report] |SUCCESS| pw95646 [dpdk-dev] " 0-day Robot
2021-07-11 10:11 [dpdk-test-report] |WARNING| pw95646 [PATCH] [v2] " dpdklab

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=20210711093108.214EA120F1F@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=fengchengwen@huawei.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).