From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw140931 [PATCH v4 5/5] vhost: manage FD with epoll
Date: Tue, 11 Jun 2024 15:42:21 +0200 (CEST) [thread overview]
Message-ID: <20240611134221.85489124124@dpdk.org> (raw)
In-Reply-To: <20240611133957.72032-6-maxime.coquelin@redhat.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/140931
_coding style OK_
next prev parent reply other threads:[~2024-06-11 13:42 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240611133957.72032-6-maxime.coquelin@redhat.com>
2024-06-11 13:14 ` |SUCCESS| pw140927-140931 " qemudev
2024-06-11 13:19 ` qemudev
2024-06-11 13:42 ` checkpatch [this message]
2024-06-11 14:44 ` |SUCCESS| pw140931 " 0-day Robot
2024-06-11 18:42 ` |SUCCESS| pw140927-140931 [PATCH] [v4,5/5] vhost: manage FD with epo dpdklab
2024-06-11 18:47 ` dpdklab
2024-06-11 18:50 ` dpdklab
2024-06-11 18:51 ` dpdklab
2024-06-11 18:54 ` dpdklab
2024-06-11 19:05 ` dpdklab
2024-06-13 1:10 ` dpdklab
2024-06-13 1:12 ` dpdklab
2024-06-13 1:12 ` |FAILURE| " dpdklab
2024-06-13 1:12 ` |SUCCESS| " dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:14 ` dpdklab
2024-06-13 1:14 ` |FAILURE| " dpdklab
2024-06-13 1:14 ` |SUCCESS| " dpdklab
2024-06-13 1:15 ` |FAILURE| " dpdklab
2024-06-13 1:16 ` |SUCCESS| " dpdklab
2024-06-13 1:16 ` |FAILURE| " dpdklab
2024-06-13 1:16 ` |SUCCESS| " dpdklab
2024-06-13 1:16 ` dpdklab
2024-06-13 1:16 ` dpdklab
2024-06-13 1:17 ` dpdklab
2024-06-13 1:17 ` dpdklab
2024-06-13 1:18 ` dpdklab
2024-06-13 1:18 ` dpdklab
2024-06-13 1:19 ` dpdklab
2024-06-13 1:19 ` dpdklab
2024-06-13 1:19 ` |FAILURE| " dpdklab
2024-06-13 1:20 ` |SUCCESS| " dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:20 ` |FAILURE| " dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:21 ` dpdklab
2024-06-13 1:21 ` |SUCCESS| " dpdklab
2024-06-13 1:21 ` |FAILURE| " dpdklab
2024-06-13 1:21 ` dpdklab
2024-06-13 1:21 ` |SUCCESS| " dpdklab
2024-06-13 1:21 ` |FAILURE| " dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:22 ` |SUCCESS| " dpdklab
2024-06-13 1:22 ` |FAILURE| " dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:23 ` |SUCCESS| " dpdklab
2024-06-13 1:23 ` |FAILURE| " dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` |SUCCESS| " dpdklab
2024-06-13 1:23 ` |FAILURE| " dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:28 ` dpdklab
2024-06-13 1:28 ` dpdklab
2024-06-13 1:28 ` dpdklab
2024-06-13 1:28 ` dpdklab
2024-06-13 1:28 ` dpdklab
2024-06-13 1:28 ` |SUCCESS| " 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=20240611134221.85489124124@dpdk.org \
--to=checkpatch@dpdk.org \
--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).