From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138441 [PATCH] app/testpmd: dump TCI when asking for VLAN insertion
Date: Mon, 18 Mar 2024 15:42:26 +0800 [thread overview]
Message-ID: <202403180742.42I7gQKh2346511@localhost.localdomain> (raw)
In-Reply-To: <20240318080237.2170473-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138441
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Mon, 18 Mar 2024 09:02:37 +0100
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 20db7deeb5131e46e859e212b334e8bef88ae701
138441 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
next parent reply other threads:[~2024-03-18 8:07 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318080237.2170473-1-david.marchand@redhat.com>
2024-03-18 7:42 ` qemudev [this message]
2024-03-18 7:47 ` qemudev
2024-03-18 8:03 ` checkpatch
2024-03-18 9:03 ` 0-day Robot
2024-03-18 9:05 ` |SUCCESS| pw138441 [PATCH] app/testpmd: dump TCI when asking for VLA dpdklab
2024-03-18 9:05 ` dpdklab
2024-03-18 9:09 ` dpdklab
2024-03-18 9:10 ` dpdklab
2024-03-18 9:10 ` dpdklab
2024-03-18 9:10 ` dpdklab
2024-03-18 9:11 ` dpdklab
2024-03-18 9:11 ` dpdklab
2024-03-18 9:11 ` dpdklab
2024-03-18 9:11 ` dpdklab
2024-03-18 9:11 ` dpdklab
2024-03-18 9:12 ` dpdklab
2024-03-18 9:12 ` dpdklab
2024-03-18 9:12 ` dpdklab
2024-03-18 9:13 ` dpdklab
2024-03-18 9:13 ` dpdklab
2024-03-18 9:13 ` dpdklab
2024-03-18 9:13 ` dpdklab
2024-03-18 9:14 ` dpdklab
2024-03-18 9:14 ` dpdklab
2024-03-18 9:14 ` dpdklab
2024-03-18 9:14 ` dpdklab
2024-03-18 9:14 ` dpdklab
2024-03-18 9:14 ` dpdklab
2024-03-18 9:15 ` dpdklab
2024-03-18 9:15 ` dpdklab
2024-03-18 9:15 ` dpdklab
2024-03-18 9:15 ` dpdklab
2024-03-18 9:15 ` dpdklab
2024-03-18 9:15 ` dpdklab
2024-03-18 9:16 ` dpdklab
2024-03-18 9:16 ` dpdklab
2024-03-18 9:16 ` dpdklab
2024-03-18 9:16 ` dpdklab
2024-03-18 9:16 ` dpdklab
2024-03-18 9:17 ` dpdklab
2024-03-18 9:17 ` dpdklab
2024-03-18 9:17 ` dpdklab
2024-03-18 9:17 ` dpdklab
2024-03-18 9:17 ` dpdklab
2024-03-18 9:17 ` dpdklab
2024-03-18 9:17 ` dpdklab
2024-03-18 9:18 ` dpdklab
2024-03-18 9:18 ` dpdklab
2024-03-18 9:18 ` dpdklab
2024-03-18 9:18 ` dpdklab
2024-03-18 9:18 ` dpdklab
2024-03-18 9:20 ` dpdklab
2024-03-18 9:20 ` dpdklab
2024-03-18 9:20 ` dpdklab
2024-03-18 9:20 ` dpdklab
2024-03-18 9:21 ` dpdklab
2024-03-18 9:21 ` dpdklab
2024-03-18 9:21 ` dpdklab
2024-03-18 9:21 ` dpdklab
2024-03-18 9:22 ` dpdklab
2024-03-18 9:22 ` dpdklab
2024-03-18 9:22 ` dpdklab
2024-03-18 9:22 ` dpdklab
2024-03-18 9:22 ` dpdklab
2024-03-18 9:23 ` dpdklab
2024-03-18 9:24 ` dpdklab
2024-03-18 9:24 ` dpdklab
2024-03-18 9:25 ` dpdklab
2024-03-18 9:46 ` dpdklab
2024-03-18 9:47 ` dpdklab
2024-03-18 10:32 ` dpdklab
2024-03-20 9:24 ` dpdklab
2024-03-20 10:00 ` 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=202403180742.42I7gQKh2346511@localhost.localdomain \
--to=qemudev@loongson.cn \
--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).