From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122861-122863 [PATCH v5 3/3] app/testpmd: add IPv6 routing extension header in raw encap
Date: Thu, 2 Feb 2023 11:00:39 +0800 [thread overview]
Message-ID: <202302020300.31230dsf2755647@localhost.localdomain> (raw)
In-Reply-To: <20230201113511.2362188-4-rongweil@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122863
_Compilation OK_
Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Wed, 1 Feb 2023 13:35:09 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 27d0bd43801528ac9dffd2e6119ad4733c7baa61
122861-122863 --> 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 prev parent reply other threads:[~2023-02-02 3:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230201113511.2362188-4-rongweil@nvidia.com>
2023-02-01 11:36 ` |SUCCESS| pw122863 " checkpatch
2023-02-01 12:39 ` 0-day Robot
2023-02-02 3:00 ` qemudev [this message]
2023-02-02 3:01 ` |SUCCESS| pw122861-122863 " qemudev
2023-02-01 14:03 |SUCCESS| pw122861-122863 [PATCH] [v5, " dpdklab
2023-02-01 14:05 dpdklab
2023-02-01 14:06 dpdklab
2023-02-01 14:08 dpdklab
2023-02-01 14:20 dpdklab
2023-02-01 14:28 dpdklab
2023-02-01 16:15 dpdklab
2023-02-02 0:35 dpdklab
2023-02-02 2:18 dpdklab
2023-02-02 2:20 dpdklab
2023-02-02 2:20 dpdklab
2023-02-02 2:21 dpdklab
2023-02-02 2:21 dpdklab
2023-02-02 2:21 dpdklab
2023-02-02 2:21 dpdklab
2023-02-02 2:21 dpdklab
2023-02-02 2:21 dpdklab
2023-02-02 2:22 dpdklab
2023-02-02 13:04 dpdklab
2023-02-02 13:51 dpdklab
2023-02-02 14:56 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=202302020300.31230dsf2755647@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).