automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: |WARNING| pw137339 [PATCH v4] vhost: enhance virtqueue access lock asserts
Date: Tue, 27 Feb 2024 11:39:52 +0100 (CET)	[thread overview]
Message-ID: <20240227103952.28DBA122320@dpdk.org> (raw)
In-Reply-To: <20240227103903.1338151-1-david.marchand@redhat.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/137339

_coding style issues_


ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#123: FILE: lib/vhost/vhost_user.c:69:
+#define VHOST_MESSAGE_HANDLERS \
+VHOST_MESSAGE_HANDLER(VHOST_USER_NONE, NULL, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_GET_FEATURES, vhost_user_get_features, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_FEATURES, vhost_user_set_features, false, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_OWNER, vhost_user_set_owner, false, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_RESET_OWNER, vhost_user_reset_owner, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_MEM_TABLE, vhost_user_set_mem_table, true, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_LOG_BASE, vhost_user_set_log_base, true, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_LOG_FD, vhost_user_set_log_fd, true, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_VRING_NUM, vhost_user_set_vring_num, false, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_VRING_ADDR, vhost_user_set_vring_addr, false, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_VRING_BASE, vhost_user_set_vring_base, false, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_GET_VRING_BASE, vhost_user_get_vring_base, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_VRING_KICK, vhost_user_set_vring_kick, true, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_VRING_CALL, vhost_user_set_vring_call, true, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_VRING_ERR, vhost_user_set_vring_err, true, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_GET_PROTOCOL_FEATURES, vhost_user_get_protocol_features, \
+	false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_PROTOCOL_FEATURES, vhost_user_set_protocol_features, \
+	false, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_GET_QUEUE_NUM, vhost_user_get_queue_num, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_VRING_ENABLE, vhost_user_set_vring_enable, false, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SEND_RARP, vhost_user_send_rarp, false, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_NET_SET_MTU, vhost_user_net_set_mtu, false, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_BACKEND_REQ_FD, vhost_user_set_req_fd, true, true) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_IOTLB_MSG, vhost_user_iotlb_msg, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_GET_CONFIG, vhost_user_get_config, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_CONFIG, vhost_user_set_config, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_POSTCOPY_ADVISE, vhost_user_set_postcopy_advise, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_POSTCOPY_LISTEN, vhost_user_set_postcopy_listen, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_POSTCOPY_END, vhost_user_postcopy_end, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_GET_INFLIGHT_FD, vhost_user_get_inflight_fd, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_INFLIGHT_FD, vhost_user_set_inflight_fd, true, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_SET_STATUS, vhost_user_set_status, false, false) \
+VHOST_MESSAGE_HANDLER(VHOST_USER_GET_STATUS, vhost_user_get_status, false, false)

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#159: FILE: lib/vhost/vhost_user.c:105:
+#define VHOST_MESSAGE_HANDLER(id, handler, accepts_fd, lock_all_qps) \
+	id ## _LOCK_ALL_QPS = lock_all_qps,

WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#176: FILE: lib/vhost/vhost_user.c:122:
+	static_assert(id ## _LOCK_ALL_QPS == true, \

total: 2 errors, 1 warnings, 189 lines checked

  parent reply	other threads:[~2024-02-27 10:39 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240227103903.1338151-1-david.marchand@redhat.com>
2024-02-27 10:20 ` |SUCCESS| " qemudev
2024-02-27 10:25 ` qemudev
2024-02-27 10:39 ` checkpatch [this message]
2024-02-27 11:45 ` 0-day Robot
2024-02-27 19:45 ` |SUCCESS| pw137339 [PATCH] [v4] vhost: enhance virtqueue access lock dpdklab
2024-02-27 19:46 ` dpdklab
2024-02-27 19:46 ` dpdklab
2024-02-27 19:46 ` dpdklab
2024-02-27 19:47 ` dpdklab
2024-02-27 19:55 ` dpdklab
2024-02-27 19:55 ` dpdklab
2024-02-27 19:55 ` dpdklab
2024-02-27 19:56 ` dpdklab
2024-02-27 19:56 ` dpdklab
2024-02-27 19:57 ` dpdklab
2024-02-27 19:58 ` dpdklab
2024-02-27 19:58 ` dpdklab
2024-02-27 19:59 ` dpdklab
2024-02-27 19:59 ` dpdklab
2024-02-27 19:59 ` dpdklab
2024-02-27 19:59 ` dpdklab
2024-02-27 20:00 ` dpdklab
2024-02-27 20:00 ` dpdklab
2024-02-27 20:02 ` dpdklab
2024-02-27 20:02 ` dpdklab
2024-02-27 20:03 ` dpdklab
2024-02-27 20:03 ` dpdklab
2024-02-27 20:04 ` dpdklab
2024-02-27 20:04 ` dpdklab
2024-02-27 20:04 ` dpdklab
2024-02-27 20:04 ` dpdklab
2024-02-27 20:05 ` dpdklab
2024-02-27 20:05 ` dpdklab
2024-02-27 20:05 ` dpdklab
2024-02-27 20:05 ` dpdklab
2024-02-27 20:06 ` dpdklab
2024-02-27 20:06 ` dpdklab
2024-02-27 20:06 ` dpdklab
2024-02-27 20:06 ` dpdklab
2024-02-27 20:13 ` dpdklab
2024-02-27 20:23 ` dpdklab
2024-02-27 20:42 ` dpdklab
2024-02-27 20:45 ` dpdklab
2024-02-27 20:46 ` dpdklab
2024-02-27 20:57 ` dpdklab
2024-02-27 20:58 ` dpdklab
2024-02-27 21:00 ` dpdklab
2024-02-27 21:01 ` dpdklab
2024-02-27 21:03 ` dpdklab
2024-02-27 23:30 ` dpdklab
2024-02-28  1:09 ` dpdklab
2024-02-28  7:04 ` dpdklab
2024-02-28  7:08 ` dpdklab
2024-02-28  8:56 ` dpdklab
2024-02-28 17:30 ` dpdklab
2024-02-29 10:44 ` dpdklab
2024-02-29 10:49 ` dpdklab
2024-02-29 10:54 ` dpdklab
2024-02-29 10:59 ` dpdklab

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=20240227103952.28DBA122320@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).