From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Spike Du <spiked@nvidia.com>
Subject: |WARNING| pw111741 [PATCH v3 3/7] ethdev: introduce Rx queue based limit watermark
Date: Tue, 24 May 2022 17:22:17 +0200 (CEST) [thread overview]
Message-ID: <20220524152217.E839D120945@dpdk.org> (raw)
In-Reply-To: <20220524152041.737154-4-spiked@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/111741
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#248: FILE: lib/ethdev/rte_ethdev.h:1935:
+ * Per-queue Rx limit watermark defined as percentage of Rx queue$
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#248: FILE: lib/ethdev/rte_ethdev.h:1935:
+ /**
+ * Per-queue Rx limit watermark defined as percentage of Rx queue
ERROR:CODE_INDENT: code indent should use tabs where possible
#249: FILE: lib/ethdev/rte_ethdev.h:1936:
+ * size. If Rx queue receives traffic higher than this percentage,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#250: FILE: lib/ethdev/rte_ethdev.h:1937:
+ * the event RTE_ETH_EVENT_RX_LWM is triggered.$
ERROR:CODE_INDENT: code indent should use tabs where possible
#251: FILE: lib/ethdev/rte_ethdev.h:1938:
+ * Value 0 means watermark monitoring is disabled, no event is$
ERROR:CODE_INDENT: code indent should use tabs where possible
#252: FILE: lib/ethdev/rte_ethdev.h:1939:
+ * triggered.$
ERROR:CODE_INDENT: code indent should use tabs where possible
#253: FILE: lib/ethdev/rte_ethdev.h:1940:
+ */$
WARNING:TYPO_SPELLING: 'circularly' may be misspelled - perhaps 'circular'?
#291: FILE: lib/ethdev/rte_ethdev.h:3712:
+ * The function queries all queues in the port circularly until one
total: 6 errors, 2 warnings, 189 lines checked
parent reply other threads:[~2022-05-24 15:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220524152041.737154-4-spiked@nvidia.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=20220524152217.E839D120945@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=spiked@nvidia.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).