From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Danylo Vodopianov <dvo-plv@napatech.com>
Subject: |WARNING| pw153937 [PATCH v3 1/1] vhost: handle virtqueue locking for memory hotplug
Date: Mon, 2 Jun 2025 10:43:32 +0200 (CEST) [thread overview]
Message-ID: <20250602084332.5AAFE125279@dpdk.org> (raw)
In-Reply-To: <20250602084025.1881768-2-dvo-plv@napatech.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153937
_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")'
#133:
127f9c6f7b78 ("vhost: handle memory hotplug with vDPA devices"),
total: 1 errors, 0 warnings, 14 lines checked
next prev parent reply other threads:[~2025-06-02 8:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250602084025.1881768-2-dvo-plv@napatech.com>
2025-06-02 8:21 ` |SUCCESS| " qemudev
2025-06-02 8:25 ` qemudev
2025-06-02 8:43 ` checkpatch [this message]
2025-06-02 9:26 ` |PENDING| pw153937 [PATCH] [v3,1/1] vhost: handle virtqueue locking dpdklab
2025-06-02 9:35 ` dpdklab
2025-06-02 9:37 ` |SUCCESS| " dpdklab
2025-06-02 9:57 ` |PENDING| " dpdklab
2025-06-02 10:05 ` |SUCCESS| pw153937 [PATCH v3 1/1] vhost: handle virtqueue locking for memory hotplug 0-day Robot
2025-06-02 10:33 ` |SUCCESS| pw153937 [PATCH] [v3,1/1] vhost: handle virtqueue locking dpdklab
2025-06-02 10:39 ` dpdklab
2025-06-02 10:46 ` dpdklab
2025-06-02 10:52 ` |WARNING| " dpdklab
2025-06-02 10:52 ` dpdklab
2025-06-02 11:23 ` |SUCCESS| " dpdklab
2025-06-02 12:04 ` dpdklab
2025-06-02 13:07 ` dpdklab
2025-06-04 21:16 ` 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=20250602084332.5AAFE125279@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).