From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
Subject: |WARNING| pw114585 [PATCH] net/ring: add umonitor callback
Date: Wed, 3 Aug 2022 16:25:30 +0200 (CEST) [thread overview]
Message-ID: <20220803142530.63578120775@dpdk.org> (raw)
In-Reply-To: <20220803142845.2221915-1-herakliusz.lipiec@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/114585
_coding style issues_
ERROR:POINTER_LOCATION: "foo* bar" should be "foo *bar"
#90: FILE: drivers/net/ring/rte_eth_ring.c:295:
+eth_get_monitor_addr(void* rx_queue, struct rte_power_monitor_cond *pmc)
CHECK:SPACING: No space is necessary after a cast
#92: FILE: drivers/net/ring/rte_eth_ring.c:297:
+ struct rte_ring *rng = ((struct ring_queue*) rx_queue)->rng;
ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#92: FILE: drivers/net/ring/rte_eth_ring.c:297:
+ struct rte_ring *rng = ((struct ring_queue*) rx_queue)->rng;
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#96: FILE: drivers/net/ring/rte_eth_ring.c:301:
+ * */
total: 2 errors, 1 warnings, 1 checks, 35 lines checked
next parent reply other threads:[~2022-08-03 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220803142845.2221915-1-herakliusz.lipiec@intel.com>
2022-08-03 14:25 ` checkpatch [this message]
2022-08-03 15:59 ` |SUCCESS| " 0-day Robot
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=20220803142530.63578120775@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=herakliusz.lipiec@intel.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).