automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Christophe Fontaine <cfontain@redhat.com>
Subject: |WARNING| pw106957 [PATCH v2 1/1] vhost: move fds outside of VhostUserMessage
Date: Mon,  7 Feb 2022 11:22:41 +0100 (CET)	[thread overview]
Message-ID: <20220207102241.EB3FD120715@dpdk.org> (raw)
In-Reply-To: <20220207102129.59170-2-cfontain@redhat.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#121: FILE: lib/vhost/vhost_crypto.c:470:
+	switch (ctx->msg.request.master) {

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#183: FILE: lib/vhost/vhost_user.c:127:
+		vhost_message_str[ctx->msg.request.master],

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#443: FILE: lib/vhost/vhost_user.c:1201:
+	if (ack_ctx.msg.request.master != VHOST_USER_SET_MEM_TABLE) {

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#446: FILE: lib/vhost/vhost_user.c:1203:
+				dev->ifname, ack_ctx.msg.request.master);

ERROR:SPACING: space required after that ',' (ctx:VxV)
#1179: FILE: lib/vhost/vhost_user.c:2831:
+send_vhost_reply(struct virtio_net *dev,int sockfd, struct vhu_msg_context *ctx)
                                        ^

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1200: FILE: lib/vhost/vhost_user.c:2845:
+send_vhost_slave_message(struct virtio_net *dev,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1211: FILE: lib/vhost/vhost_user.c:2853:
+	ret = send_vhost_message(dev, dev->slave_req_fd, ctx);

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1226: FILE: lib/vhost/vhost_user.c:2869:
+	switch (ctx->msg.request.master) {

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1269: FILE: lib/vhost/vhost_user.c:2969:
+	request = ctx.msg.request.master;

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1373: FILE: lib/vhost/vhost_user.c:3172:
+	if (msg_reply.msg.request.slave != ctx->msg.request.slave) {

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1373: FILE: lib/vhost/vhost_user.c:3172:
+	if (msg_reply.msg.request.slave != ctx->msg.request.slave) {

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1376: FILE: lib/vhost/vhost_user.c:3174:
+				dev->ifname, msg_reply.msg.request.slave, ctx->msg.request.slave);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1376: FILE: lib/vhost/vhost_user.c:3174:
+				dev->ifname, msg_reply.msg.request.slave, ctx->msg.request.slave);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1400: FILE: lib/vhost/vhost_user.c:3192:
+			.request.slave = VHOST_USER_SLAVE_IOTLB_MSG,

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#1400: FILE: lib/vhost/vhost_user.c:3192:
+			.request.slave = VHOST_USER_SLAVE_IOTLB_MSG,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1412: FILE: lib/vhost/vhost_user.c:3203:
+	ret = send_vhost_message(dev, dev->slave_req_fd, &ctx);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1426: FILE: lib/vhost/vhost_user.c:3219:
+			.request.slave = VHOST_USER_SLAVE_CONFIG_CHANGE_MSG,

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#1426: FILE: lib/vhost/vhost_user.c:3219:
+			.request.slave = VHOST_USER_SLAVE_CONFIG_CHANGE_MSG,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1437: FILE: lib/vhost/vhost_user.c:3228:
+	ret = send_vhost_slave_message(dev, &ctx);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1445: FILE: lib/vhost/vhost_user.c:3235:
+	return process_slave_message_reply(dev, &ctx);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1463: FILE: lib/vhost/vhost_user.c:3258:
+			.request.slave = VHOST_USER_SLAVE_VRING_HOST_NOTIFIER_MSG,

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#1463: FILE: lib/vhost/vhost_user.c:3258:
+			.request.slave = VHOST_USER_SLAVE_VRING_HOST_NOTIFIER_MSG,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1485: FILE: lib/vhost/vhost_user.c:3276:
+	ret = send_vhost_slave_message(dev, &ctx);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1493: FILE: lib/vhost/vhost_user.c:3283:
+	return process_slave_message_reply(dev, &ctx);

WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email address mismatch: 'From: Christophe Fontaine <christophefontaine@mac.com>' != 'Signed-off-by: Christophe Fontaine <cfontain@redhat.com>'

total: 1 errors, 24 warnings, 1340 lines checked

       reply	other threads:[~2022-02-07 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220207102129.59170-2-cfontain@redhat.com>
2022-02-07 10:22 ` checkpatch [this message]
2022-02-07 12:19 ` |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=20220207102241.EB3FD120715@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=cfontain@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).