From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129649 [PATCH v2] MAINTAINERS: add status information
Date: Wed, 19 Jul 2023 23:56:01 +0800 [thread overview]
Message-ID: <202307191556.36JFu1tq516951@localhost.localdomain> (raw)
In-Reply-To: <20230719160735.6054-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/129649
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed, 19 Jul 2023 09:07:35 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: b2a0271188f3428ad5dc1ea600e1e2254b9d6781
129649 --> 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-07-19 16:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230719160735.6054-1-stephen@networkplumber.org>
2023-07-19 15:56 ` qemudev [this message]
2023-07-19 16:00 ` qemudev
2023-07-19 16:09 ` checkpatch
2023-07-19 16:58 ` 0-day Robot
2023-07-19 17:13 |SUCCESS| pw129649 [PATCH] [v2] " dpdklab
2023-07-19 17:13 dpdklab
2023-07-19 17:15 dpdklab
2023-07-19 17:17 dpdklab
2023-07-19 17:19 dpdklab
2023-07-19 17:21 dpdklab
2023-07-19 17:30 dpdklab
2023-07-19 17:32 dpdklab
2023-07-19 17:37 dpdklab
2023-07-19 17:37 dpdklab
2023-07-19 17:42 dpdklab
2023-07-19 17:50 dpdklab
2023-07-19 17:50 dpdklab
2023-07-19 17:53 dpdklab
2023-07-19 18:01 dpdklab
2023-07-19 18:08 dpdklab
2023-07-19 18:09 dpdklab
2023-07-19 18:12 dpdklab
2023-07-19 18:13 dpdklab
2023-07-19 18:21 dpdklab
2023-07-19 19:10 dpdklab
2023-07-19 19:10 dpdklab
2023-07-19 19:26 dpdklab
2023-07-19 19:59 dpdklab
2023-07-19 20:08 dpdklab
2023-07-19 20:13 dpdklab
2023-07-19 20:18 dpdklab
2023-07-19 20:35 dpdklab
2023-07-19 20:48 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=202307191556.36JFu1tq516951@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).