From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andy Pei <andy.pei@intel.com>
Subject: |WARNING| pw106470 [PATCH 15/15] vhost: make sure each queue callfd is configured
Date: Tue, 25 Jan 2022 07:55:08 +0100 (CET) [thread overview]
Message-ID: <20220125065508.73291120715@dpdk.org> (raw)
In-Reply-To: <1643093258-47258-16-git-send-email-andy.pei@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/106470
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#63:
During the vhost data path building process, qemu will create a call fd at first,
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#92: FILE: lib/vhost/vhost_user.c:3151:
+ /**
+ ** when VIRTIO_DEV_VDPA_CONFIGURED already configured
WARNING:TYPO_SPELLING: 'configed' may be misspelled - perhaps 'configured'?
#94: FILE: lib/vhost/vhost_user.c:3153:
+ ** make sure the call fd of each queue is configed correctly.
total: 0 errors, 3 warnings, 27 lines checked
next parent reply other threads:[~2022-01-25 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1643093258-47258-16-git-send-email-andy.pei@intel.com>
2022-01-25 6:55 ` checkpatch [this message]
2022-01-25 8:20 ` |FAILURE| " 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=20220125065508.73291120715@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).