From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138854 [PATCH 4/4] net/virtio: fix shadow control queue allocation
Date: Wed, 27 Mar 2024 06:45:08 -0400 [thread overview]
Message-ID: <20240327104508.1402802-1-robot@bytheb.org> (raw)
In-Reply-To: <20240327094032.2400951-5-maxime.coquelin@redhat.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138854/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8449968477
next prev parent reply other threads:[~2024-03-27 10:45 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240327094032.2400951-5-maxime.coquelin@redhat.com>
2024-03-27 9:18 ` |SUCCESS| pw138851-138854 " qemudev
2024-03-27 9:23 ` qemudev
2024-03-27 9:43 ` |SUCCESS| pw138854 " checkpatch
2024-03-27 10:45 ` 0-day Robot [this message]
2024-03-27 12:20 ` |SUCCESS| pw138851-138854 [PATCH] [4/4] net/virtio: fix shadow contr dpdklab
2024-03-27 12:21 ` dpdklab
2024-03-27 12:30 ` dpdklab
2024-03-27 12:32 ` dpdklab
2024-03-27 12:32 ` dpdklab
2024-03-27 12:33 ` dpdklab
2024-03-27 12:33 ` dpdklab
2024-03-27 12:33 ` dpdklab
2024-03-27 12:33 ` dpdklab
2024-03-27 12:34 ` dpdklab
2024-03-27 12:34 ` dpdklab
2024-03-27 12:34 ` dpdklab
2024-03-27 12:34 ` dpdklab
2024-03-27 12:35 ` dpdklab
2024-03-27 12:35 ` dpdklab
2024-03-27 12:35 ` dpdklab
2024-03-27 12:35 ` dpdklab
2024-03-27 12:35 ` dpdklab
2024-03-27 12:36 ` dpdklab
2024-03-27 12:36 ` dpdklab
2024-03-27 12:36 ` dpdklab
2024-03-27 12:36 ` dpdklab
2024-03-27 12:37 ` dpdklab
2024-03-27 12:37 ` dpdklab
2024-03-27 12:37 ` dpdklab
2024-03-27 12:38 ` dpdklab
2024-03-27 12:38 ` dpdklab
2024-03-27 12:45 ` dpdklab
2024-03-27 12:47 ` dpdklab
2024-03-27 12:47 ` dpdklab
2024-03-27 12:47 ` dpdklab
2024-03-27 12:48 ` dpdklab
2024-03-27 12:50 ` dpdklab
2024-03-27 12:50 ` dpdklab
2024-03-27 12:50 ` dpdklab
2024-03-27 12:51 ` dpdklab
2024-03-27 12:51 ` dpdklab
2024-03-27 12:51 ` |FAILURE| " dpdklab
2024-03-27 12:52 ` |SUCCESS| " dpdklab
2024-03-27 12:53 ` dpdklab
2024-03-27 12:54 ` |FAILURE| " dpdklab
2024-03-27 12:56 ` |SUCCESS| " dpdklab
2024-03-27 12:57 ` dpdklab
2024-03-27 12:58 ` dpdklab
2024-03-27 12:58 ` dpdklab
2024-03-27 12:59 ` dpdklab
2024-03-27 13:00 ` dpdklab
2024-03-27 13:00 ` dpdklab
2024-03-27 13:01 ` dpdklab
2024-03-27 13:02 ` dpdklab
2024-03-27 13:05 ` dpdklab
2024-03-27 13:05 ` dpdklab
2024-03-27 13:06 ` dpdklab
2024-03-27 13:07 ` dpdklab
2024-03-27 13:07 ` dpdklab
2024-03-27 13:09 ` dpdklab
2024-03-27 13:10 ` dpdklab
2024-03-27 13:11 ` dpdklab
2024-03-27 13:11 ` dpdklab
2024-03-27 13:12 ` dpdklab
2024-03-27 13:17 ` dpdklab
2024-03-27 13:18 ` dpdklab
2024-03-27 13:22 ` dpdklab
2024-03-27 13:22 ` dpdklab
2024-03-27 13:23 ` dpdklab
2024-03-27 13:24 ` dpdklab
2024-03-27 13:25 ` dpdklab
2024-03-27 13:25 ` dpdklab
2024-03-27 13:28 ` dpdklab
2024-03-27 13:31 ` dpdklab
2024-03-27 13:31 ` dpdklab
2024-03-27 13:33 ` dpdklab
2024-03-27 13:37 ` dpdklab
2024-03-27 13:42 ` dpdklab
2024-03-27 13:43 ` dpdklab
2024-03-27 13:46 ` dpdklab
2024-03-27 13:46 ` dpdklab
2024-03-27 13:49 ` dpdklab
2024-03-27 13:56 ` dpdklab
2024-03-27 15:12 ` dpdklab
2024-03-27 15:20 ` dpdklab
2024-03-27 15:26 ` dpdklab
2024-03-27 15:57 ` dpdklab
2024-04-02 8:49 ` dpdklab
2024-04-02 8:53 ` dpdklab
2024-04-02 8:58 ` |FAILURE| " dpdklab
2024-04-02 9:01 ` |SUCCESS| " dpdklab
2024-04-02 9:21 ` |FAILURE| " 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=20240327104508.1402802-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).