From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw140933 [PATCH v2 2/2] conf schema
Date: Tue, 11 Jun 2024 13:24:01 -0400 [thread overview]
Message-ID: <20240611172401.432119-1-robot@bytheb.org> (raw)
In-Reply-To: <20240611161606.23881-5-dmarx@iol.unh.edu>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/140933/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9469585437
next prev parent reply other threads:[~2024-06-11 17:24 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240611161606.23881-5-dmarx@iol.unh.edu>
2024-06-11 15:57 ` |SUCCESS| pw140932-140933 " qemudev
2024-06-11 16:01 ` qemudev
2024-06-11 16:21 ` |WARNING| pw140933 " checkpatch
2024-06-11 17:24 ` 0-day Robot [this message]
2024-06-11 18:10 ` |SUCCESS| pw140932-140933 [PATCH] [v2,2/2] " dpdklab
2024-06-11 18:36 ` dpdklab
2024-06-11 18:37 ` dpdklab
2024-06-11 18:38 ` dpdklab
2024-06-11 18:40 ` dpdklab
2024-06-11 18:43 ` dpdklab
2024-06-13 1:08 ` dpdklab
2024-06-13 1:08 ` dpdklab
2024-06-13 1:08 ` dpdklab
2024-06-13 1:08 ` dpdklab
2024-06-13 1:09 ` dpdklab
2024-06-13 1:09 ` dpdklab
2024-06-13 1:09 ` dpdklab
2024-06-13 1:09 ` dpdklab
2024-06-13 1:09 ` dpdklab
2024-06-13 1:09 ` dpdklab
2024-06-13 1:09 ` dpdklab
2024-06-13 1:09 ` dpdklab
2024-06-13 1:10 ` dpdklab
2024-06-13 1:10 ` dpdklab
2024-06-13 1:10 ` dpdklab
2024-06-13 1:11 ` dpdklab
2024-06-13 1:11 ` dpdklab
2024-06-13 1:11 ` dpdklab
2024-06-13 1:11 ` dpdklab
2024-06-13 1:11 ` dpdklab
2024-06-13 1:11 ` dpdklab
2024-06-13 1:11 ` dpdklab
2024-06-13 1:11 ` dpdklab
2024-06-13 1:12 ` dpdklab
2024-06-13 1:12 ` dpdklab
2024-06-13 1:12 ` dpdklab
2024-06-13 1:12 ` dpdklab
2024-06-13 1:12 ` dpdklab
2024-06-13 1:12 ` dpdklab
2024-06-13 1:12 ` dpdklab
2024-06-13 1:12 ` dpdklab
2024-06-13 1:12 ` dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:14 ` dpdklab
2024-06-13 1:14 ` dpdklab
2024-06-13 1:14 ` dpdklab
2024-06-13 1:14 ` dpdklab
2024-06-13 1:14 ` dpdklab
2024-06-13 1:15 ` dpdklab
2024-06-13 1:15 ` dpdklab
2024-06-13 1:15 ` dpdklab
2024-06-13 1:15 ` dpdklab
2024-06-13 1:15 ` dpdklab
2024-06-13 1:15 ` dpdklab
2024-06-13 1:15 ` dpdklab
2024-06-13 1:15 ` dpdklab
2024-06-13 1:15 ` dpdklab
2024-06-13 1:16 ` dpdklab
2024-06-13 1:16 ` dpdklab
2024-06-13 1:16 ` dpdklab
2024-06-13 1:16 ` dpdklab
2024-06-13 1:16 ` dpdklab
2024-06-13 1:16 ` dpdklab
2024-06-13 1:16 ` dpdklab
2024-06-13 1:16 ` 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:17 ` dpdklab
2024-06-13 1:17 ` 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:18 ` 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 ` dpdklab
2024-06-13 1:19 ` dpdklab
2024-06-13 1:19 ` dpdklab
2024-06-13 1:19 ` dpdklab
2024-06-13 1:19 ` dpdklab
2024-06-13 1:19 ` dpdklab
2024-06-13 1:19 ` dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:21 ` dpdklab
2024-06-13 1:21 ` dpdklab
2024-06-13 1:21 ` dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:28 ` 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=20240611172401.432119-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).