From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw129674 [PATCH v3] tap: fix build of TAP BPF program
Date: Fri, 21 Jul 2023 01:26:35 +0200 (CEST) [thread overview]
Message-ID: <20230720232635.0F33412092E@dpdk.org> (raw)
In-Reply-To: <20230720232549.63619-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/129674
_coding style issues_
WARNING:CONSTANT_CONVERSION: __constant_htons should be htons
#220: FILE: drivers/net/tap/bpf/bpf_api.h:44:
+# define htons(X) __constant_htons((X))
WARNING:CONSTANT_CONVERSION: __constant_ntohs should be ntohs
#224: FILE: drivers/net/tap/bpf/bpf_api.h:48:
+# define ntohs(X) __constant_ntohs((X))
WARNING:INLINE: plain inline is preferred over __inline__
#235: FILE: drivers/net/tap/bpf/bpf_api.h:59:
+#ifndef __inline__
WARNING:INLINE: plain inline is preferred over __inline__
#236: FILE: drivers/net/tap/bpf/bpf_api.h:60:
+# define __inline__ __attribute__((always_inline))
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#297: FILE: drivers/net/tap/bpf/bpf_api.h:121:
+# define __BPF_FUNC(NAME, ...) \
+ (* NAME)(__VA_ARGS__) __maybe_unused
CHECK:MACRO_ARG_PRECEDENCE: Macro argument 'NAME' may be better as '(NAME)' to avoid precedence issues
#297: FILE: drivers/net/tap/bpf/bpf_api.h:121:
+# define __BPF_FUNC(NAME, ...) \
+ (* NAME)(__VA_ARGS__) __maybe_unused
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#302: FILE: drivers/net/tap/bpf/bpf_api.h:126:
+# define BPF_FUNC(NAME, ...) \
+ __BPF_FUNC(NAME, __VA_ARGS__) = (void *) BPF_FUNC_##NAME
CHECK:SPACING: No space is necessary after a cast
#303: FILE: drivers/net/tap/bpf/bpf_api.h:127:
+ __BPF_FUNC(NAME, __VA_ARGS__) = (void *) BPF_FUNC_##NAME
WARNING:TRACE_PRINTK: Do not use trace_printk() in production code (this can be ignored if built only with a debug config option)
#328: FILE: drivers/net/tap/bpf/bpf_api.h:152:
+ trace_printk(____fmt, sizeof(____fmt), ##__VA_ARGS__); \
CHECK:SPACING: No space is necessary after a cast
#381: FILE: drivers/net/tap/bpf/bpf_api.h:205:
+ (void *) BPF_FUNC_perf_event_output;
CHECK:SPACING: No space is necessary after a cast
#403: FILE: drivers/net/tap/bpf/bpf_api.h:227:
+# define lock_xadd(ptr, val) ((void) __sync_fetch_and_add(ptr, val))
WARNING:TYPO_SPELLING: 'useable' may be misspelled - perhaps 'usable'?
#418: FILE: drivers/net/tap/bpf/bpf_api.h:242:
+/* FIXME: __builtin_memcmp() is not yet fully useable unless llvm bug
WARNING:IF_0: Consider removing the code enclosed by this #if 0 and its #endif
#422: FILE: drivers/net/tap/bpf/bpf_api.h:246:
+#if 0
total: 2 errors, 7 warnings, 4 checks, 457 lines checked
Warning in drivers/net/tap/bpf/bpf_api.h:
Using compiler attribute directly
Warning in drivers/net/tap/bpf/bpf_api.h:
Using __sync_xxx builtins
next prev parent reply other threads:[~2023-07-20 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230720232549.63619-1-stephen@networkplumber.org>
2023-07-20 23:13 ` |SUCCESS| " qemudev
2023-07-20 23:17 ` qemudev
2023-07-20 23:26 ` checkpatch [this message]
2023-07-21 0:18 ` 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=20230720232635.0F33412092E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.org \
--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).