From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124448-124449 [PATCH v3 2/2] net/mlx5: add MPLS tunnel support for HWS
Date: Thu, 23 Feb 2023 15:42:06 +0800 [thread overview]
Message-ID: <202302230742.31N7g6fK2816989@localhost.localdomain> (raw)
In-Reply-To: <20230223074734.3315320-3-michaelba@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124449
_Compilation OK_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Thu, 23 Feb 2023 09:47:33 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 34c8d1d3bef546f03159407a7af314176456d629
124448-124449 --> 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-02-23 7:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230223074734.3315320-3-michaelba@nvidia.com>
2023-02-23 7:42 ` qemudev [this message]
2023-02-23 7:46 ` qemudev
2023-02-23 7:49 ` |SUCCESS| pw124449 " checkpatch
2023-02-23 10:39 ` 0-day Robot
2023-02-23 16:56 |SUCCESS| pw124448-124449 [PATCH] [v3, " dpdklab
2023-02-23 16:56 dpdklab
2023-02-23 17:00 dpdklab
2023-02-23 17:04 dpdklab
2023-02-23 17:11 dpdklab
2023-02-23 17:11 dpdklab
2023-02-23 17:16 dpdklab
2023-02-23 17:28 dpdklab
2023-02-23 17:31 dpdklab
2023-02-23 17:35 dpdklab
2023-02-23 19:08 dpdklab
2023-02-23 19:13 dpdklab
2023-02-23 19:16 dpdklab
2023-02-23 19:45 dpdklab
2023-02-23 19:45 dpdklab
2023-02-23 19:46 dpdklab
2023-02-23 19:47 dpdklab
2023-02-23 19:47 dpdklab
2023-02-23 19:49 dpdklab
2023-02-23 19:50 dpdklab
2023-02-23 19:50 dpdklab
2023-02-23 19:54 dpdklab
2023-02-23 19:55 dpdklab
2023-02-23 19: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=202302230742.31N7g6fK2816989@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).