From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: |WARNING| pw113466 [PATCH 4/4] vhost: prefix logs with context
Date: Mon, 27 Jun 2022 11:28:39 +0200 (CEST) [thread overview]
Message-ID: <20220627092839.44C0D1230A5@dpdk.org> (raw)
In-Reply-To: <20220627092728.78214-5-david.marchand@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/113466
_coding style issues_
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#955: FILE: lib/vhost/vhost.h:632:
+#define VHOST_LOG_DATA(prefix, level, fmt, args...) \
(void)((RTE_LOG_ ## level <= RTE_LOG_DP_LEVEL) ? \
rte_log(RTE_LOG_ ## level, vhost_data_log_level, \
+ "VHOST_DATA: (%s):" fmt, prefix, ##args) : \
0)
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1009: FILE: lib/vhost/vhost_user.c:98:
+ expected_fds, vhost_message_handlers[ctx->msg.request.master].description,
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1478: FILE: lib/vhost/vhost_user.c:1157:
+ ack_ctx.msg.request.master);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#2049: FILE: lib/vhost/vhost_user.c:2409:
+ "invalid file descriptor for slave channel (%d)
", fd);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#2381: FILE: lib/vhost/vhost_user.c:3211:
+ "vhost read slave message reply failed
");
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#2395: FILE: lib/vhost/vhost_user.c:3222:
+ msg_reply.msg.request.slave, ctx->msg.request.slave);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#2395: FILE: lib/vhost/vhost_user.c:3222:
+ msg_reply.msg.request.slave, ctx->msg.request.slave);
total: 1 errors, 6 warnings, 2735 lines checked
next parent reply other threads:[~2022-06-27 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220627092728.78214-5-david.marchand@redhat.com>
2022-06-27 9:28 ` checkpatch [this message]
2022-06-27 10:39 ` |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=20220627092839.44C0D1230A5@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=david.marchand@redhat.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).