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| pw106235 [PATCH 1/1] vhost: Move fds outside of VhostUserMessage
Date: Sun, 23 Jan 2022 13:00:42 +0100 (CET)	[thread overview]
Message-ID: <20220123120042.334C9120767@dpdk.org> (raw)
In-Reply-To: <20220123115927.76130-2-cfontain@redhat.com>

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

_coding style issues_


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

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

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

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#429: FILE: lib/vhost/vhost_user.c:1200:
+				ack_msg.msg.request.master);

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

total: 0 errors, 23 warnings, 1328 lines checked

       reply	other threads:[~2022-01-23 12:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220123115927.76130-2-cfontain@redhat.com>
2022-01-23 12:00 ` checkpatch [this message]
2022-01-23 13: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=20220123120042.334C9120767@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).