From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw142669 [V3] app/testpmd: restore VXLAN-GPE support
Date: Tue, 23 Jul 2024 16:27:57 +0200 (CEST) [thread overview]
Message-ID: <20240723142757.35536124124@dpdk.org> (raw)
In-Reply-To: <20240723142649.44013-1-gavinl@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/142669
_coding style OK_
next prev parent reply other threads:[~2024-07-23 14:27 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240723142649.44013-1-gavinl@nvidia.com>
2024-07-23 14:01 ` qemudev
2024-07-23 14:06 ` qemudev
2024-07-23 14:27 ` checkpatch [this message]
2024-07-23 15:23 ` 0-day Robot
2024-07-23 23:20 ` |PENDING| pw142669 [PATCH] [V3] app/testpmd: restore VXLAN-GPE suppo dpdklab
2024-07-23 23:23 ` |SUCCESS| " dpdklab
2024-07-23 23:28 ` dpdklab
2024-07-23 23:30 ` dpdklab
2024-07-23 23:33 ` dpdklab
2024-07-23 23:41 ` dpdklab
2024-07-23 23:44 ` dpdklab
2024-07-23 23:57 ` dpdklab
2024-07-24 0:02 ` dpdklab
2024-07-24 0:07 ` dpdklab
2024-07-24 0:07 ` dpdklab
2024-07-24 0:10 ` |PENDING| " dpdklab
2024-07-24 0:10 ` |SUCCESS| " dpdklab
2024-07-24 0:12 ` dpdklab
2024-07-24 0:14 ` |PENDING| " dpdklab
2024-07-24 0:14 ` dpdklab
2024-07-24 0:18 ` |SUCCESS| " dpdklab
2024-07-24 0:20 ` dpdklab
2024-07-24 0:21 ` |PENDING| " dpdklab
2024-07-24 0:22 ` dpdklab
2024-07-24 0:22 ` dpdklab
2024-07-24 0:23 ` dpdklab
2024-07-24 0:24 ` dpdklab
2024-07-24 0:31 ` dpdklab
2024-07-24 0:31 ` dpdklab
2024-07-24 0:34 ` dpdklab
2024-07-24 0:35 ` dpdklab
2024-07-24 0:43 ` dpdklab
2024-07-24 0:50 ` dpdklab
2024-07-24 0:52 ` dpdklab
2024-07-24 0:52 ` dpdklab
2024-07-24 0:55 ` |SUCCESS| " dpdklab
2024-07-24 0:57 ` dpdklab
2024-07-24 0:58 ` dpdklab
2024-07-24 1:01 ` |PENDING| " dpdklab
2024-07-24 1:01 ` |SUCCESS| " dpdklab
2024-07-24 1:02 ` |PENDING| " dpdklab
2024-07-24 1:04 ` dpdklab
2024-07-24 1:04 ` dpdklab
2024-07-24 1:04 ` dpdklab
2024-07-24 1:04 ` dpdklab
2024-07-24 1:08 ` dpdklab
2024-07-24 1:11 ` dpdklab
2024-07-24 1:18 ` dpdklab
2024-07-24 1:28 ` dpdklab
2024-07-24 1:28 ` dpdklab
2024-07-24 1:33 ` dpdklab
2024-07-24 1:35 ` dpdklab
2024-07-24 1:36 ` dpdklab
2024-07-24 1:37 ` dpdklab
2024-07-24 1:38 ` dpdklab
2024-07-24 1:38 ` dpdklab
2024-07-24 1:38 ` dpdklab
2024-07-24 1:39 ` dpdklab
2024-07-24 1:39 ` dpdklab
2024-07-24 1:39 ` dpdklab
2024-07-24 1:39 ` dpdklab
2024-07-24 1:40 ` dpdklab
2024-07-24 1:40 ` dpdklab
2024-07-24 1:42 ` |SUCCESS| " dpdklab
2024-07-24 1:43 ` |PENDING| " dpdklab
2024-07-24 1:43 ` dpdklab
2024-07-24 1:43 ` dpdklab
2024-07-24 1:46 ` |SUCCESS| " dpdklab
2024-07-24 1:46 ` dpdklab
2024-07-24 1:47 ` |PENDING| " dpdklab
2024-07-24 1:48 ` dpdklab
2024-07-24 1:51 ` dpdklab
2024-07-24 1:53 ` dpdklab
2024-07-24 1:55 ` dpdklab
2024-07-24 1:55 ` dpdklab
2024-07-24 1:57 ` dpdklab
2024-07-24 2:00 ` dpdklab
2024-07-24 2:00 ` dpdklab
2024-07-24 2:13 ` dpdklab
2024-07-24 2:14 ` dpdklab
2024-07-24 2:16 ` dpdklab
2024-07-24 2:17 ` dpdklab
2024-07-24 2:17 ` |SUCCESS| " dpdklab
2024-07-24 2:18 ` |PENDING| " dpdklab
2024-07-24 2:19 ` dpdklab
2024-07-24 2:19 ` dpdklab
2024-07-24 2:19 ` dpdklab
2024-07-24 2:21 ` dpdklab
2024-07-24 2:21 ` dpdklab
2024-07-24 2:21 ` dpdklab
2024-07-24 2:21 ` dpdklab
2024-07-24 2:22 ` dpdklab
2024-07-24 2:22 ` dpdklab
2024-07-24 2:23 ` dpdklab
2024-07-24 2:24 ` dpdklab
2024-07-24 2:24 ` dpdklab
2024-07-24 2:25 ` dpdklab
2024-07-24 2:27 ` dpdklab
2024-07-24 2:27 ` dpdklab
2024-07-24 2:28 ` dpdklab
2024-07-24 2:28 ` dpdklab
2024-07-24 2:29 ` dpdklab
2024-07-24 2:29 ` dpdklab
2024-07-24 2:29 ` dpdklab
2024-07-24 2:30 ` dpdklab
2024-07-24 2:33 ` dpdklab
2024-07-24 2:34 ` dpdklab
2024-07-24 2:35 ` dpdklab
2024-07-24 2:41 ` |SUCCESS| " dpdklab
2024-07-24 2:59 ` |PENDING| " dpdklab
2024-07-24 3:02 ` dpdklab
2024-07-24 3:14 ` |SUCCESS| " dpdklab
2024-07-24 3:35 ` |PENDING| " dpdklab
2024-07-24 3:44 ` dpdklab
2024-07-24 3:53 ` |SUCCESS| " dpdklab
2024-07-25 10:05 ` 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=20240723142757.35536124124@dpdk.org \
--to=checkpatch@dpdk.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).