From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Danylo Vodopianov <dvo-plv@napatech.com>
Subject: |WARNING| pw153863 [PATCH v1 1/1] vhost: handle virtqueue locking for memory hotplug
Date: Thu, 29 May 2025 14:32:43 +0200 (CEST) [thread overview]
Message-ID: <20250529123243.9A8B5125275@dpdk.org> (raw)
In-Reply-To: <20250529123102.1875027-2-dvo-plv@napatech.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153863
_coding style issues_
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 127f9c6f7b78 ("vhost: handle memory hotplug with vDPA devices")'
#144:
127f9c6f7b78 ("vhost: handle memory hotplug with vDPA devices"),
total: 1 errors, 0 warnings, 14 lines checked
next prev parent reply other threads:[~2025-05-29 12:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250529123102.1875027-2-dvo-plv@napatech.com>
2025-05-29 12:13 ` |SUCCESS| " qemudev
2025-05-29 12:18 ` qemudev
2025-05-29 12:32 ` checkpatch [this message]
2025-05-29 13:43 ` 0-day Robot
2025-05-29 23:34 ` |SUCCESS| pw153863 [PATCH] [v1,1/1] vhost: handle virtqueue locking dpdklab
2025-05-29 23:45 ` dpdklab
2025-05-30 1:46 ` |PENDING| " dpdklab
2025-05-30 1:54 ` dpdklab
2025-05-30 2:11 ` |SUCCESS| " dpdklab
2025-05-30 2:12 ` dpdklab
2025-05-30 2:12 ` dpdklab
2025-05-30 2:13 ` dpdklab
2025-05-30 2:14 ` dpdklab
2025-05-30 2:14 ` dpdklab
2025-05-30 2:15 ` dpdklab
2025-05-30 2:15 ` dpdklab
2025-05-30 2:40 ` |PENDING| " dpdklab
2025-05-30 4:44 ` |WARNING| " dpdklab
2025-05-30 4:49 ` dpdklab
2025-05-30 4:50 ` dpdklab
2025-05-30 6:08 ` |SUCCESS| " dpdklab
2025-05-30 10:32 ` dpdklab
2025-05-30 11:48 ` |WARNING| " dpdklab
2025-05-30 22:08 ` dpdklab
2025-05-30 22:09 ` dpdklab
2025-05-31 0:22 ` |SUCCESS| " dpdklab
2025-05-31 3:01 ` dpdklab
2025-05-31 3:03 ` dpdklab
2025-06-04 13:45 ` dpdklab
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=20250529123243.9A8B5125275@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=dvo-plv@napatech.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).