From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138956 [PATCH v2 4/4] net/virtio-user: fix control queue allocation
Date: Thu, 28 Mar 2024 10:05:31 -0400 [thread overview]
Message-ID: <20240328140531.3471102-1-robot@bytheb.org> (raw)
In-Reply-To: <20240328130813.3696005-5-maxime.coquelin@redhat.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138956/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8468041167
next prev parent reply other threads:[~2024-03-28 14:05 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240328130813.3696005-5-maxime.coquelin@redhat.com>
2024-03-28 12:45 ` |SUCCESS| pw138955-138956 " qemudev
2024-03-28 12:50 ` qemudev
2024-03-28 13:10 ` |SUCCESS| pw138956 " checkpatch
2024-03-28 14:05 ` 0-day Robot [this message]
2024-03-28 14:48 ` |SUCCESS| pw138955-138956 [PATCH] [v2,4/4] net/virtio-user: fix cont dpdklab
2024-03-28 14:50 ` dpdklab
2024-03-28 14:50 ` dpdklab
2024-03-28 14:50 ` dpdklab
2024-03-28 14:51 ` dpdklab
2024-03-28 14:51 ` dpdklab
2024-03-28 14:52 ` dpdklab
2024-03-28 14:52 ` dpdklab
2024-03-28 14:53 ` dpdklab
2024-03-28 14:54 ` dpdklab
2024-03-28 14:55 ` dpdklab
2024-03-28 14:55 ` dpdklab
2024-03-28 14:56 ` dpdklab
2024-03-28 14:57 ` dpdklab
2024-03-28 15:02 ` dpdklab
2024-03-28 15:09 ` dpdklab
2024-03-28 15:15 ` dpdklab
2024-03-28 15:42 ` dpdklab
2024-03-28 15:46 ` dpdklab
2024-03-28 15:56 ` dpdklab
2024-03-28 16:01 ` dpdklab
2024-03-28 16:02 ` dpdklab
2024-03-28 16:05 ` dpdklab
2024-03-28 16:05 ` dpdklab
2024-03-28 16:07 ` dpdklab
2024-03-28 16:09 ` dpdklab
2024-03-28 16:10 ` dpdklab
2024-03-28 16:10 ` dpdklab
2024-03-28 16:11 ` dpdklab
2024-03-28 16:11 ` dpdklab
2024-03-28 16:13 ` dpdklab
2024-03-28 16:13 ` dpdklab
2024-03-28 16:14 ` dpdklab
2024-03-28 16:15 ` dpdklab
2024-03-28 16:15 ` dpdklab
2024-03-28 16:16 ` dpdklab
2024-03-28 16:16 ` dpdklab
2024-03-28 16:18 ` dpdklab
2024-03-28 16:19 ` dpdklab
2024-03-28 16:19 ` dpdklab
2024-03-28 16:20 ` dpdklab
2024-03-28 16:22 ` dpdklab
2024-03-28 16:23 ` dpdklab
2024-03-28 16:24 ` dpdklab
2024-03-28 16:25 ` dpdklab
2024-03-28 16:27 ` dpdklab
2024-03-28 16:27 ` dpdklab
2024-03-28 16:28 ` dpdklab
2024-03-28 16:28 ` |FAILURE| " dpdklab
2024-03-28 16:30 ` |SUCCESS| " dpdklab
2024-03-28 16:31 ` dpdklab
2024-03-28 16:32 ` dpdklab
2024-03-28 16:32 ` dpdklab
2024-03-28 16:39 ` |FAILURE| " dpdklab
2024-03-28 16:39 ` |SUCCESS| " dpdklab
2024-03-28 16:39 ` dpdklab
2024-03-28 16:40 ` dpdklab
2024-03-28 16:41 ` dpdklab
2024-03-28 16:43 ` dpdklab
2024-03-28 16:43 ` dpdklab
2024-03-28 16:43 ` |FAILURE| " dpdklab
2024-03-28 16:45 ` |SUCCESS| " dpdklab
2024-03-28 16:45 ` |FAILURE| " dpdklab
2024-03-28 16:45 ` |SUCCESS| " dpdklab
2024-03-28 16:46 ` dpdklab
2024-03-28 16:50 ` dpdklab
2024-03-28 16:58 ` dpdklab
2024-03-28 16:58 ` dpdklab
2024-03-28 16:59 ` |FAILURE| " dpdklab
2024-03-28 16:59 ` |SUCCESS| " dpdklab
2024-03-28 17:00 ` dpdklab
2024-03-28 17:00 ` |FAILURE| " dpdklab
2024-03-28 17:01 ` |SUCCESS| " dpdklab
2024-03-28 17:02 ` dpdklab
2024-03-28 17:06 ` dpdklab
2024-03-28 17:07 ` dpdklab
2024-03-28 17:07 ` dpdklab
2024-03-28 17:16 ` dpdklab
2024-03-28 17:27 ` dpdklab
2024-03-28 17:33 ` dpdklab
2024-03-28 18:09 ` dpdklab
2024-03-28 18:10 ` dpdklab
2024-04-02 16:47 ` dpdklab
2024-04-02 16:52 ` dpdklab
2024-04-02 16:55 ` dpdklab
2024-04-02 17:02 ` dpdklab
2024-04-02 17:25 ` 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=20240328140531.3471102-1-robot@bytheb.org \
--to=robot@bytheb.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).