From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw142717 [RFC v1 3/3] dts: conf schema VXLAN gpe support
Date: Thu, 25 Jul 2024 14:03:18 -0400 [thread overview]
Message-ID: <20240725180318.2198609-1-robot@bytheb.org> (raw)
In-Reply-To: <20240725162325.20933-4-dmarx@iol.unh.edu>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/142717/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10098111014
next prev parent reply other threads:[~2024-07-25 18:03 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240725162325.20933-4-dmarx@iol.unh.edu>
2024-07-25 15:58 ` |SUCCESS| pw142715-142717 " qemudev
2024-07-25 16:02 ` qemudev
2024-07-25 16:25 ` |SUCCESS| pw142717 " checkpatch
2024-07-25 17:07 ` |SUCCESS| pw142715-142717 [PATCH] [RFC,v1,3/3] dts: conf schema VXLA dpdklab
2024-07-25 17:09 ` dpdklab
2024-07-25 17:10 ` dpdklab
2024-07-25 17:12 ` dpdklab
2024-07-25 17:12 ` dpdklab
2024-07-25 17:14 ` dpdklab
2024-07-25 17:18 ` dpdklab
2024-07-25 17:18 ` dpdklab
2024-07-25 17:18 ` dpdklab
2024-07-25 17:38 ` |PENDING| " dpdklab
2024-07-25 17:39 ` |SUCCESS| " dpdklab
2024-07-25 17:40 ` dpdklab
2024-07-25 17:43 ` dpdklab
2024-07-25 17:47 ` |PENDING| " dpdklab
2024-07-25 17:47 ` dpdklab
2024-07-25 17:48 ` dpdklab
2024-07-25 17:48 ` dpdklab
2024-07-25 17:49 ` dpdklab
2024-07-25 17:50 ` dpdklab
2024-07-25 17:51 ` dpdklab
2024-07-25 17:51 ` dpdklab
2024-07-25 17:52 ` dpdklab
2024-07-25 17:52 ` dpdklab
2024-07-25 17:52 ` dpdklab
2024-07-25 17:52 ` dpdklab
2024-07-25 17:53 ` |SUCCESS| " dpdklab
2024-07-25 17:55 ` |PENDING| " dpdklab
2024-07-25 17:55 ` dpdklab
2024-07-25 17:55 ` dpdklab
2024-07-25 17:55 ` dpdklab
2024-07-25 17:56 ` dpdklab
2024-07-25 17:56 ` dpdklab
2024-07-25 17:56 ` dpdklab
2024-07-25 17:57 ` dpdklab
2024-07-25 17:57 ` dpdklab
2024-07-25 17:58 ` dpdklab
2024-07-25 17:58 ` dpdklab
2024-07-25 17:58 ` dpdklab
2024-07-25 17:58 ` dpdklab
2024-07-25 18:00 ` dpdklab
2024-07-25 18:02 ` dpdklab
2024-07-25 18:03 ` 0-day Robot [this message]
2024-07-25 18:03 ` dpdklab
2024-07-25 18:03 ` dpdklab
2024-07-25 18:05 ` dpdklab
2024-07-25 18:05 ` dpdklab
2024-07-25 18:06 ` dpdklab
2024-07-25 18:07 ` dpdklab
2024-07-25 18:07 ` dpdklab
2024-07-25 18:07 ` dpdklab
2024-07-25 18:07 ` dpdklab
2024-07-25 18:08 ` dpdklab
2024-07-25 18:08 ` dpdklab
2024-07-25 18:11 ` dpdklab
2024-07-25 18:13 ` dpdklab
2024-07-25 18:14 ` dpdklab
2024-07-25 18:15 ` dpdklab
2024-07-25 18:15 ` dpdklab
2024-07-25 18:15 ` dpdklab
2024-07-25 18:15 ` dpdklab
2024-07-25 18:17 ` dpdklab
2024-07-25 18:18 ` |SUCCESS| " dpdklab
2024-07-25 18:18 ` |PENDING| " dpdklab
2024-07-25 18:19 ` dpdklab
2024-07-25 18:19 ` dpdklab
2024-07-25 18:19 ` dpdklab
2024-07-25 18:22 ` dpdklab
2024-07-25 18:23 ` dpdklab
2024-07-25 18:23 ` dpdklab
2024-07-25 18:24 ` dpdklab
2024-07-25 18:26 ` dpdklab
2024-07-25 18:30 ` dpdklab
2024-07-25 18:32 ` dpdklab
2024-07-25 18:33 ` dpdklab
2024-07-25 18:34 ` dpdklab
2024-07-25 18:35 ` dpdklab
2024-07-25 18:35 ` dpdklab
2024-07-25 18:35 ` dpdklab
2024-07-25 18:36 ` dpdklab
2024-07-25 18:36 ` dpdklab
2024-07-25 18:36 ` dpdklab
2024-07-25 18:36 ` dpdklab
2024-07-25 18:37 ` dpdklab
2024-07-25 18:38 ` |SUCCESS| " dpdklab
2024-07-25 18:38 ` |PENDING| " dpdklab
2024-07-25 18:39 ` dpdklab
2024-07-25 18:40 ` dpdklab
2024-07-25 18:40 ` dpdklab
2024-07-25 18:41 ` dpdklab
2024-07-25 18:42 ` dpdklab
2024-07-25 18:43 ` |SUCCESS| " dpdklab
2024-07-25 18:44 ` |PENDING| " dpdklab
2024-07-25 18:44 ` |SUCCESS| " dpdklab
2024-07-25 18:45 ` |PENDING| " dpdklab
2024-07-25 18:46 ` dpdklab
2024-07-25 18:47 ` dpdklab
2024-07-25 18:49 ` dpdklab
2024-07-25 18:50 ` |SUCCESS| " dpdklab
2024-07-25 18:55 ` |PENDING| " dpdklab
2024-07-25 19:12 ` dpdklab
2024-07-25 19:16 ` |SUCCESS| " dpdklab
2024-07-26 14:27 ` dpdklab
2024-07-26 18:38 ` dpdklab
2024-07-26 18:46 ` 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=20240725180318.2198609-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).