From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wenbo Cao <caowenbo@mucse.com>
Subject: |WARNING| pw151993 [PATCH v15 05/29] net/rnp: add device init and uninit
Date: Tue, 25 Feb 2025 09:48:08 +0100 (CET) [thread overview]
Message-ID: <20250225084808.63228127817@dpdk.org> (raw)
In-Reply-To: <1740472886-30411-6-git-send-email-caowenbo@mucse.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/151993
_coding style issues_
WARNING:BAD_SIGN_OFF: Duplicate signature
#52:
Signed-off-by: Wenbo Cao <caowenbo@mucse.com>
WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#586: FILE: drivers/net/rnp/base/rnp_hw.h:74:
+ bool msg_alloced;
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'f' - possible side-effects?
#592: FILE: drivers/net/rnp/base/rnp_hw.h:80:
+#define rnp_call_hwif_impl(port, f, arg...) \
+ (((f) != NULL) ? ((f) (port, arg)) : (-ENODEV))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'x' - possible side-effects?
#1078: FILE: drivers/net/rnp/base/rnp_osdep.h:39:
+#define ffs(x) (rte_fls_u32((x) & (-x)))
CHECK:CAMELCASE: Avoid CamelCase: <PRIu64>
#1132: FILE: drivers/net/rnp/base/rnp_osdep.h:103:
+ snprintf(z_name, sizeof(z_name), "rnp_dma_%" PRIu64,
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#1146: FILE: drivers/net/rnp/base/rnp_osdep.h:117:
+ "%"PRIu64, mz->name, mem->pa);
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#1156: FILE: drivers/net/rnp/base/rnp_osdep.h:127:
+ "%"PRIu64, ((const struct rte_memzone *)mem->mz)->name,
total: 0 errors, 2 warnings, 5 checks, 1423 lines checked
Warning in drivers/net/rnp/base/rnp_hw.h:
Do not use variadic argument pack in macros
parent reply other threads:[~2025-02-25 8:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1740472886-30411-6-git-send-email-caowenbo@mucse.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=20250225084808.63228127817@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=caowenbo@mucse.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).