From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw131619 [PATCH] testpmd: add hairpin-map parameter
Date: Tue, 19 Sep 2023 17:52:28 +0800 [thread overview]
Message-ID: <202309190952.38J9qSw41930921@localhost.localdomain> (raw)
In-Reply-To: <20230919101006.19936-1-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/131619
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tue, 19 Sep 2023 13:10:06 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: a4e700a878e7fa2651fd718e61f7228c3277e556
131619 --> 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:[~2023-09-19 10:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230919101006.19936-1-getelson@nvidia.com>
2023-09-19 9:52 ` qemudev [this message]
2023-09-19 9:56 ` qemudev
2023-09-19 10:11 ` |WARNING| " checkpatch
2023-09-19 11:50 ` |FAILURE| " 0-day Robot
2023-09-19 10:43 |SUCCESS| " dpdklab
2023-09-19 10:48 dpdklab
2023-09-19 10:49 dpdklab
2023-09-19 10:49 dpdklab
2023-09-19 10:49 dpdklab
2023-09-19 10:50 dpdklab
2023-09-19 10:50 dpdklab
2023-09-19 10:50 dpdklab
2023-09-19 10:52 dpdklab
2023-09-19 10:52 dpdklab
2023-09-19 10:52 dpdklab
2023-09-19 11:03 dpdklab
2023-09-19 11:04 dpdklab
2023-09-19 11:04 dpdklab
2023-09-19 11:04 dpdklab
2023-09-19 11:04 dpdklab
2023-09-19 11:12 dpdklab
2023-09-19 11:13 dpdklab
2023-09-19 11:13 dpdklab
2023-09-19 11:13 dpdklab
2023-09-19 11:15 dpdklab
2023-09-19 11:15 dpdklab
2023-09-19 11:15 dpdklab
2023-09-19 11:17 dpdklab
2023-09-19 11:26 dpdklab
2023-09-19 11:31 dpdklab
2023-09-19 11:34 dpdklab
2023-09-19 11:35 dpdklab
2023-09-19 11:41 dpdklab
2023-09-19 12:07 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=202309190952.38J9qSw41930921@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).