automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: |WARNING| pw106502 [PATCH v2 4/9] vhost: improve Vhost-user layer logs
Date: Tue, 25 Jan 2022 12:27:13 +0100 (CET)	[thread overview]
Message-ID: <20220125112713.61943120715@dpdk.org> (raw)
In-Reply-To: <20220125112457.166434-5-maxime.coquelin@redhat.com>

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

_coding style issues_


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

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1272: FILE: lib/vhost/vhost_user.c:2441:
+		VHOST_LOG_CONFIG(ERR, "(%s) invalid file descriptor for slave channel (%d)
",

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1567: FILE: lib/vhost/vhost_user.c:3142:
+	ret = read_vhost_message(dev, dev->slave_req_fd, &msg_reply);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1572: FILE: lib/vhost/vhost_user.c:3145:
+			VHOST_LOG_CONFIG(ERR, "(%s) vhost read slave message reply failed
",

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

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

total: 0 errors, 6 warnings, 1430 lines checked

           reply	other threads:[~2022-01-25 11:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20220125112457.166434-5-maxime.coquelin@redhat.com>]

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=20220125112713.61943120715@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=maxime.coquelin@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).