From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126533-126548 [PATCH v3 15/15] common/idpf/base: update license and README
Date: Wed, 26 Apr 2023 18:19:31 +0800 [thread overview]
Message-ID: <202304261019.33QAJVGL2226650@localhost.localdomain> (raw)
In-Reply-To: <20230426102259.205992-16-wenjing.qiao@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126548
_Compilation OK_
Submitter: Wenjing Qiao <wenjing.qiao@intel.com>
Date: Wed, 26 Apr 2023 06:22:45 -0400
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 318b2f8d4c1842dd13ed4e208c530ea3e132c8c8
126533-126548 --> 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-04-26 10:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230426102259.205992-16-wenjing.qiao@intel.com>
2023-04-26 10:19 ` qemudev [this message]
2023-04-26 10:23 ` qemudev
2023-04-26 10:30 ` |WARNING| pw126548 " checkpatch
2023-04-26 11:39 ` |SUCCESS| " 0-day Robot
2023-04-27 1:30 |SUCCESS| pw126533-126548 [PATCH] [v3, " dpdklab
2023-04-27 1:34 dpdklab
2023-04-27 1:35 dpdklab
2023-04-27 1:42 dpdklab
2023-04-27 2:12 dpdklab
2023-04-27 2:26 dpdklab
2023-04-27 3:35 dpdklab
2023-04-27 3:36 dpdklab
2023-04-27 3:36 dpdklab
2023-04-27 3:51 dpdklab
2023-04-27 3:56 dpdklab
2023-04-27 3:58 dpdklab
2023-04-27 3:58 dpdklab
2023-04-27 4:02 dpdklab
2023-04-27 4:08 dpdklab
2023-04-27 4:09 dpdklab
2023-04-27 4:12 dpdklab
2023-04-27 4:17 dpdklab
2023-04-27 4:19 dpdklab
2023-04-27 6:26 dpdklab
2023-04-27 6:26 dpdklab
2023-04-27 6:27 dpdklab
2023-04-27 20:35 dpdklab
2023-04-27 23:22 dpdklab
2023-04-28 15:53 dpdklab
2023-04-28 17:02 dpdklab
2023-04-28 20:03 dpdklab
2023-04-28 20:10 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=202304261019.33QAJVGL2226650@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).