From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw142657 [V2] app/testpmd: restore VXLAN-GPE support
Date: Tue, 23 Jul 2024 04:43:59 -0400 [thread overview]
Message-ID: <20240723084359.924914-1-robot@bytheb.org> (raw)
In-Reply-To: <20240723073730.33272-1-gavinl@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/142657/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10055120618
next prev parent reply other threads:[~2024-07-23 9:32 UTC|newest]
Thread overview: 109+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240723073730.33272-1-gavinl@nvidia.com>
2024-07-23 7:14 ` qemudev
2024-07-23 7:19 ` qemudev
2024-07-23 7:41 ` checkpatch
2024-07-23 8:43 ` 0-day Robot [this message]
2024-07-23 13:01 ` |PENDING| pw142657 [PATCH] [V2] app/testpmd: restore VXLAN-GPE suppo dpdklab
2024-07-23 13:06 ` |SUCCESS| " dpdklab
2024-07-23 13:14 ` dpdklab
2024-07-23 13:14 ` dpdklab
2024-07-23 13:26 ` dpdklab
2024-07-23 13:27 ` dpdklab
2024-07-23 13:43 ` dpdklab
2024-07-23 13:57 ` dpdklab
2024-07-23 14:29 ` |PENDING| " dpdklab
2024-07-23 14:30 ` dpdklab
2024-07-23 14:31 ` dpdklab
2024-07-23 14:32 ` dpdklab
2024-07-23 14:38 ` dpdklab
2024-07-23 14:41 ` dpdklab
2024-07-23 14:41 ` dpdklab
2024-07-23 14:48 ` dpdklab
2024-07-23 14:50 ` dpdklab
2024-07-23 14:58 ` |SUCCESS| " dpdklab
2024-07-23 14:58 ` |PENDING| " dpdklab
2024-07-23 14:59 ` dpdklab
2024-07-23 15:03 ` dpdklab
2024-07-23 15:09 ` dpdklab
2024-07-23 15:09 ` dpdklab
2024-07-23 15:16 ` dpdklab
2024-07-23 15:20 ` dpdklab
2024-07-23 15:23 ` |SUCCESS| " dpdklab
2024-07-23 15:34 ` dpdklab
2024-07-23 17:21 ` |PENDING| " dpdklab
2024-07-23 17:23 ` dpdklab
2024-07-23 17:25 ` dpdklab
2024-07-23 17:25 ` dpdklab
2024-07-23 17:30 ` dpdklab
2024-07-23 17:31 ` dpdklab
2024-07-23 17:40 ` dpdklab
2024-07-23 17:42 ` dpdklab
2024-07-23 17:43 ` dpdklab
2024-07-23 17:45 ` dpdklab
2024-07-23 17:53 ` dpdklab
2024-07-23 17:59 ` dpdklab
2024-07-23 17:59 ` dpdklab
2024-07-23 17:59 ` dpdklab
2024-07-23 18:03 ` dpdklab
2024-07-23 18:03 ` dpdklab
2024-07-23 18:03 ` dpdklab
2024-07-23 18:03 ` dpdklab
2024-07-23 18:04 ` dpdklab
2024-07-23 18:05 ` dpdklab
2024-07-23 18:05 ` dpdklab
2024-07-23 18:07 ` |SUCCESS| " dpdklab
2024-07-23 18:10 ` dpdklab
2024-07-23 18:22 ` |PENDING| " dpdklab
2024-07-23 18:23 ` |SUCCESS| " dpdklab
2024-07-23 18:29 ` |PENDING| " dpdklab
2024-07-23 18:30 ` dpdklab
2024-07-23 18:30 ` dpdklab
2024-07-23 18:31 ` dpdklab
2024-07-23 18:36 ` |SUCCESS| " dpdklab
2024-07-23 18:39 ` |PENDING| " dpdklab
2024-07-23 18:42 ` dpdklab
2024-07-23 18:42 ` dpdklab
2024-07-23 18:45 ` dpdklab
2024-07-23 18:47 ` dpdklab
2024-07-23 18:48 ` dpdklab
2024-07-23 18:49 ` dpdklab
2024-07-23 18:52 ` dpdklab
2024-07-23 18:52 ` dpdklab
2024-07-23 18:53 ` dpdklab
2024-07-23 18:55 ` dpdklab
2024-07-23 19:03 ` dpdklab
2024-07-23 19:05 ` dpdklab
2024-07-23 19:06 ` dpdklab
2024-07-23 19:09 ` dpdklab
2024-07-23 19:10 ` dpdklab
2024-07-23 19:11 ` dpdklab
2024-07-23 19:11 ` dpdklab
2024-07-23 19:12 ` dpdklab
2024-07-23 19:12 ` dpdklab
2024-07-23 19:14 ` dpdklab
2024-07-23 19:16 ` dpdklab
2024-07-23 19:18 ` dpdklab
2024-07-23 19:57 ` dpdklab
2024-07-23 20:01 ` dpdklab
2024-07-23 20:04 ` dpdklab
2024-07-23 20:05 ` dpdklab
2024-07-23 20:10 ` dpdklab
2024-07-23 20:10 ` dpdklab
2024-07-23 20:14 ` dpdklab
2024-07-23 20:15 ` dpdklab
2024-07-23 20:16 ` dpdklab
2024-07-23 20:17 ` dpdklab
2024-07-23 20:19 ` dpdklab
2024-07-23 20:19 ` dpdklab
2024-07-23 20:22 ` dpdklab
2024-07-23 20:23 ` dpdklab
2024-07-23 20:24 ` dpdklab
2024-07-23 20:26 ` dpdklab
2024-07-23 20:27 ` dpdklab
2024-07-23 20:29 ` dpdklab
2024-07-23 20:31 ` dpdklab
2024-07-23 20:33 ` dpdklab
2024-07-23 20:34 ` dpdklab
2024-07-23 20:39 ` |SUCCESS| " dpdklab
2024-07-23 20:40 ` |PENDING| " dpdklab
2024-07-23 21:08 ` dpdklab
2024-07-24 17:10 ` |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=20240723084359.924914-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).