From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw140756 [PATCH v7 3/3] net/mlx5: implement VXLAN last reserved modification
Date: Wed, 5 Jun 2024 10:04:46 -0400 [thread overview]
Message-ID: <20240605140446.889487-1-robot@bytheb.org> (raw)
In-Reply-To: <20240605130419.145311-4-rongweil@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/140756/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9384993929
next prev parent reply other threads:[~2024-06-05 14:04 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240605130419.145311-4-rongweil@nvidia.com>
2024-06-05 12:41 ` |SUCCESS| pw140755-140756 " qemudev
2024-06-05 12:45 ` qemudev
2024-06-05 13:06 ` |SUCCESS| pw140756 " checkpatch
2024-06-05 14:04 ` 0-day Robot [this message]
2024-06-05 18:14 ` |SUCCESS| pw140755-140756 [PATCH] [v7,3/3] net/mlx5: implement VXLAN dpdklab
2024-06-05 18:15 ` dpdklab
2024-06-05 18:17 ` dpdklab
2024-06-05 18:18 ` dpdklab
2024-06-05 18:20 ` dpdklab
2024-06-05 18:21 ` dpdklab
2024-06-05 18:21 ` dpdklab
2024-06-05 18:25 ` dpdklab
2024-06-05 18:37 ` dpdklab
2024-06-05 18:39 ` dpdklab
2024-06-05 18:39 ` dpdklab
2024-06-05 18:40 ` dpdklab
2024-06-05 18:40 ` dpdklab
2024-06-05 18:42 ` dpdklab
2024-06-05 18:42 ` dpdklab
2024-06-05 18:43 ` dpdklab
2024-06-05 18:44 ` dpdklab
2024-06-05 18:45 ` dpdklab
2024-06-05 18:51 ` dpdklab
2024-06-05 18:56 ` dpdklab
2024-06-05 18:56 ` dpdklab
2024-06-05 18:56 ` dpdklab
2024-06-05 18:57 ` dpdklab
2024-06-05 18:57 ` dpdklab
2024-06-05 18:57 ` dpdklab
2024-06-05 19:03 ` dpdklab
2024-06-05 19:03 ` dpdklab
2024-06-05 19:04 ` dpdklab
2024-06-05 19:16 ` dpdklab
2024-06-05 19:16 ` dpdklab
2024-06-05 19:16 ` dpdklab
2024-06-05 19:17 ` dpdklab
2024-06-05 19:18 ` dpdklab
2024-06-05 19:18 ` dpdklab
2024-06-05 19:21 ` dpdklab
2024-06-05 19:29 ` dpdklab
2024-06-05 19:30 ` dpdklab
2024-06-05 19:30 ` dpdklab
2024-06-05 19:31 ` dpdklab
2024-06-05 19:31 ` dpdklab
2024-06-05 19:34 ` dpdklab
2024-06-05 19:35 ` dpdklab
2024-06-05 19:35 ` dpdklab
2024-06-05 19:35 ` dpdklab
2024-06-05 19:36 ` dpdklab
2024-06-05 19:36 ` dpdklab
2024-06-05 19:36 ` dpdklab
2024-06-05 19:36 ` dpdklab
2024-06-05 19:37 ` dpdklab
2024-06-05 19:37 ` dpdklab
2024-06-05 19:39 ` dpdklab
2024-06-05 19:39 ` dpdklab
2024-06-05 19:42 ` dpdklab
2024-06-05 19:43 ` |FAILURE| " dpdklab
2024-06-05 19:43 ` dpdklab
2024-06-05 19:48 ` |SUCCESS| " dpdklab
2024-06-05 19:50 ` dpdklab
2024-06-05 19:50 ` dpdklab
2024-06-05 19:51 ` |FAILURE| " dpdklab
2024-06-05 19:51 ` |SUCCESS| " dpdklab
2024-06-05 19:52 ` dpdklab
2024-06-05 19:53 ` dpdklab
2024-06-05 19:55 ` |FAILURE| " dpdklab
2024-06-05 19:55 ` dpdklab
2024-06-05 19:58 ` |SUCCESS| " dpdklab
2024-06-05 20:00 ` dpdklab
2024-06-05 20:00 ` dpdklab
2024-06-05 20:01 ` |FAILURE| " dpdklab
2024-06-05 20:02 ` |SUCCESS| " dpdklab
2024-06-05 20:03 ` |FAILURE| " dpdklab
2024-06-05 20:03 ` |SUCCESS| " dpdklab
2024-06-05 20:03 ` dpdklab
2024-06-05 20:03 ` |FAILURE| " dpdklab
2024-06-05 20:06 ` |SUCCESS| " dpdklab
2024-06-05 20:06 ` dpdklab
2024-06-05 20:07 ` dpdklab
2024-06-05 20:09 ` dpdklab
2024-06-05 20:11 ` dpdklab
2024-06-05 20:12 ` dpdklab
2024-06-05 20:13 ` dpdklab
2024-06-05 20:13 ` dpdklab
2024-06-05 20:14 ` dpdklab
2024-06-05 20:14 ` |FAILURE| " dpdklab
2024-06-05 20:14 ` |SUCCESS| " dpdklab
2024-06-05 20:15 ` dpdklab
2024-06-05 20:19 ` dpdklab
2024-06-05 20:21 ` dpdklab
2024-06-05 20:25 ` dpdklab
2024-06-05 20:26 ` dpdklab
2024-06-05 20:41 ` dpdklab
2024-06-05 21:14 ` dpdklab
2024-06-05 21:32 ` dpdklab
2024-06-05 21:37 ` dpdklab
2024-06-05 22:04 ` dpdklab
2024-06-06 1:35 ` dpdklab
2024-06-06 3:51 ` dpdklab
2024-06-06 3:58 ` dpdklab
2024-06-06 4:38 ` 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=20240605140446.889487-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).