From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Hao Chen <chenh@yusur.tech>
Subject: |WARNING| pw136017 [PATCH v2] vhost: fix deadlock during software live migration of VDPA in a nested virtualization environment
Date: Mon, 22 Jan 2024 04:28:55 +0100 (CET) [thread overview]
Message-ID: <20240122032855.5CFD3122B9C@dpdk.org> (raw)
In-Reply-To: <20240122032746.2749586-1-chenh@yusur.tech>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/136017
_coding style issues_
WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#61:
'vhost_user_iotlb_miss'-> send vhost message 'VHOST_USER_SLAVE_IOTLB_MSG'
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#63:
then call 'vhost_user_iotlb_rd_lock(vq)' to hold the read lock `iotlb_lock`.
WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#66:
QEMU-L2 get the 'VHOST_USER_SLAVE_IOTLB_MSG',
total: 0 errors, 3 warnings, 48 lines checked
next prev parent reply other threads:[~2024-01-22 3:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240122032746.2749586-1-chenh@yusur.tech>
2024-01-22 3:10 ` |SUCCESS| " qemudev
2024-01-22 3:14 ` qemudev
2024-01-22 3:28 ` checkpatch [this message]
2024-01-22 4:24 ` 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=20240122032855.5CFD3122B9C@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=chenh@yusur.tech \
--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).