From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andy Pei <andy.pei@intel.com>
Subject: |WARNING| pw108914 [PATCH v5 07/16] example/vdpa:add vdpa blk support in example
Date: Mon, 28 Mar 2022 10:03:38 +0200 (CEST) [thread overview]
Message-ID: <20220328080338.1283D121D58@dpdk.org> (raw)
In-Reply-To: <1648451862-123318-8-git-send-email-andy.pei@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/108914
_coding style issues_
WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#290: FILE: examples/vdpa/vhost_user.h:26:
+ (1ULL << VHOST_USER_PROTOCOL_F_SLAVE_REQ) | \
WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#292: FILE: examples/vdpa/vhost_user.h:28:
+ (1ULL << VHOST_USER_PROTOCOL_F_SLAVE_SEND_FD) | \
WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#318: FILE: examples/vdpa/vhost_user.h:54:
+ VHOST_USER_SET_SLAVE_REQ_FD = 21,
WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#331: FILE: examples/vdpa/vhost_user.h:67:
+ VHOST_USER_SLAVE_NONE = 0,
WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#332: FILE: examples/vdpa/vhost_user.h:68:
+ VHOST_USER_SLAVE_IOTLB_MSG = 1,
WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#333: FILE: examples/vdpa/vhost_user.h:69:
+ VHOST_USER_SLAVE_VRING_HOST_NOTIFIER_MSG = 3,
WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#334: FILE: examples/vdpa/vhost_user.h:70:
+ VHOST_USER_SLAVE_MAX
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#402: FILE: examples/vdpa/vhost_user.h:138:
+ uint32_t master; /* a VhostUserRequest value */
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#403: FILE: examples/vdpa/vhost_user.h:139:
+ uint32_t slave; /* a VhostUserSlaveRequest value*/
total: 0 errors, 9 warnings, 338 lines checked
parent reply other threads:[~2022-03-28 8:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1648451862-123318-8-git-send-email-andy.pei@intel.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=20220328080338.1283D121D58@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=andy.pei@intel.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).