From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125222 [PATCH v1] net/ipn3ke: fix representor name
Date: Fri, 17 Mar 2023 09:38:50 +0800 [thread overview]
Message-ID: <202303170138.32H1coI4933893@localhost.localdomain> (raw)
In-Reply-To: <20230316204456.360385-1-wei.huang@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125222
_Compilation OK_
Submitter: Wei Huang <wei.huang@intel.com>
Date: Thu, 16 Mar 2023 16:44:56 -0400
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: e7eaff0e715d5b6f9322f884a38688a0944d595b
125222 --> 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-03-17 1:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230316204456.360385-1-wei.huang@intel.com>
2023-03-17 1:38 ` qemudev [this message]
2023-03-17 1:42 ` qemudev
2023-03-17 1:45 ` checkpatch
2023-03-17 2:44 |SUCCESS| pw125222 [PATCH] [v1] " dpdklab
2023-03-17 2:55 dpdklab
2023-03-17 2:57 dpdklab
2023-03-17 3:01 dpdklab
2023-03-17 3:14 dpdklab
2023-03-17 3:18 dpdklab
2023-03-17 3:23 dpdklab
2023-03-17 3:28 dpdklab
2023-03-17 3:40 dpdklab
2023-03-17 4:46 dpdklab
2023-03-17 5:02 dpdklab
2023-03-17 5:14 dpdklab
2023-03-17 7:19 dpdklab
2023-03-19 5:21 dpdklab
2023-03-19 10:25 dpdklab
2023-03-19 20:29 dpdklab
2023-03-19 20:31 dpdklab
2023-03-19 20:44 dpdklab
2023-03-19 20:47 dpdklab
2023-03-19 20:49 dpdklab
2023-03-19 20:54 dpdklab
2023-03-19 20:57 dpdklab
2023-03-19 21:03 dpdklab
2023-03-19 21:04 dpdklab
2023-03-19 21:12 dpdklab
2023-03-19 21:14 dpdklab
2023-03-19 21:20 dpdklab
2023-03-19 21:22 dpdklab
2023-03-19 21:22 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=202303170138.32H1coI4933893@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).