From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140909 [PATCH] maintainers: update email address for PPC
Date: Mon, 10 Jun 2024 23:13:02 +0800 [thread overview]
Message-ID: <202406101513.45AFD2FA3703137@localhost.localdomain> (raw)
In-Reply-To: <20240529173420.42401-1-drc@linux.vnet.ibm.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140909
_Compilation OK_
Submitter: David Christensen <drc@linux.vnet.ibm.com>
Date: Wed, 29 May 2024 13:34:19 -0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 76cef1af8bdaeaf67a5c4ca5df3f221df994dc46
140909 --> 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:[~2024-06-10 15:41 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240529173420.42401-1-drc@linux.vnet.ibm.com>
2024-06-10 15:13 ` qemudev [this message]
2024-06-10 15:17 ` qemudev
2024-06-10 15:37 ` |WARNING| " checkpatch
2024-06-10 22:37 ` |SUCCESS| " dpdklab
2024-06-10 22:37 ` dpdklab
2024-06-10 22:38 ` dpdklab
2024-06-10 22:38 ` dpdklab
2024-06-10 22:45 ` dpdklab
2024-06-10 22:46 ` dpdklab
2024-06-12 22:47 ` dpdklab
2024-06-12 22:47 ` dpdklab
2024-06-12 22:48 ` dpdklab
2024-06-12 22:48 ` dpdklab
2024-06-12 22:49 ` dpdklab
2024-06-12 22:50 ` dpdklab
2024-06-12 22:50 ` dpdklab
2024-06-12 22:50 ` dpdklab
2024-06-12 22:51 ` dpdklab
2024-06-12 22:51 ` dpdklab
2024-06-12 22:52 ` dpdklab
2024-06-12 22:52 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:58 ` dpdklab
2024-06-12 22:58 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:35 ` 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=202406101513.45AFD2FA3703137@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).