automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andy Pei <andy.pei@intel.com>
Subject: |WARNING| pw106461 [PATCH 06/15] example/vdpa:add vdpa blk support in example
Date: Tue, 25 Jan 2022 07:55:25 +0100 (CET)	[thread overview]
Message-ID: <20220125065525.2ED87120715@dpdk.org> (raw)
In-Reply-To: <1643093258-47258-7-git-send-email-andy.pei@intel.com>

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

_coding style issues_


WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one

WARNING:TYPO_SPELLING: 'protocal' may be misspelled - perhaps 'protocol'?
#116: FILE: examples/vdpa/main.c:200:
+			"set vhost blk driver features and protocal features failed: %s
",

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#139: FILE: examples/vdpa/vdpa_blk_compact.c:2:
+/*
+**    INTEL CONFIDENTIAL

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#164: FILE: examples/vdpa/vdpa_blk_compact.c:27:
+/**
+** @file

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#197: FILE: examples/vdpa/vdpa_blk_compact.c:60:
+	fprintf(stderr, "msg is %d
", msg->request.master);

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#198: FILE: examples/vdpa/vdpa_blk_compact.c:61:
+	switch (msg->request.master) {

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#297: FILE: examples/vdpa/vdpa_blk_compact.h:2:
+/*
+**    INTEL CONFIDENTIAL

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#421: FILE: examples/vdpa/vhost_user.h:2:
+/*
+**    INTEL CONFIDENTIAL

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#466: FILE: examples/vdpa/vhost_user.h:47:
+			(1ULL << VHOST_USER_PROTOCOL_F_SLAVE_REQ) | \

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#468: FILE: examples/vdpa/vhost_user.h:49:
+			(1ULL << VHOST_USER_PROTOCOL_F_SLAVE_SEND_FD) | \

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#494: FILE: examples/vdpa/vhost_user.h:75:
+	VHOST_USER_SET_SLAVE_REQ_FD = 21,

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#507: FILE: examples/vdpa/vhost_user.h:88:
+	VHOST_USER_SLAVE_NONE = 0,

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#508: FILE: examples/vdpa/vhost_user.h:89:
+	VHOST_USER_SLAVE_IOTLB_MSG = 1,

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#509: FILE: examples/vdpa/vhost_user.h:90:
+	VHOST_USER_SLAVE_VRING_HOST_NOTIFIER_MSG = 3,

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#510: FILE: examples/vdpa/vhost_user.h:91:
+	VHOST_USER_SLAVE_MAX

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#578: FILE: examples/vdpa/vhost_user.h:159:
+		uint32_t master; /* a VhostUserRequest value */

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#579: FILE: examples/vdpa/vhost_user.h:160:
+		uint32_t slave;  /* a VhostUserSlaveRequest value*/

total: 0 errors, 17 warnings, 499 lines checked

           reply	other threads:[~2022-01-25  6:55 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1643093258-47258-7-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=20220125065525.2ED87120715@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).