From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139962-139963 [PATCH 2/2] maintainers: update for crypto performance
Date: Tue, 7 May 2024 18:59:09 +0800 [thread overview]
Message-ID: <202405071059.447Ax9231917265@localhost.localdomain> (raw)
In-Reply-To: <20240507111732.5593-2-ciara.power@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139963
_Compilation OK_
Submitter: Ciara Power <ciara.power@intel.com>
Date: Tue, 7 May 2024 11:17:31 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139962-139963 --> 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-05-07 11:27 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240507111732.5593-2-ciara.power@intel.com>
2024-05-07 10:59 ` qemudev [this message]
2024-05-07 11:03 ` qemudev
2024-05-07 11:18 ` |SUCCESS| pw139963 " checkpatch
2024-05-07 12:00 ` |SUCCESS| pw139962-139963 [PATCH] [2/2] maintainers: update for cryp dpdklab
2024-05-07 12:01 ` dpdklab
2024-05-07 12:01 ` dpdklab
2024-05-07 12:01 ` dpdklab
2024-05-07 12:02 ` dpdklab
2024-05-07 12:02 ` dpdklab
2024-05-07 12:02 ` dpdklab
2024-05-07 12:02 ` dpdklab
2024-05-07 12:03 ` dpdklab
2024-05-07 12:03 ` dpdklab
2024-05-07 12:03 ` dpdklab
2024-05-07 12:03 ` dpdklab
2024-05-07 12:04 ` dpdklab
2024-05-07 12:04 ` dpdklab
2024-05-07 12:04 ` dpdklab
2024-05-07 12:04 ` dpdklab
2024-05-07 12:04 ` dpdklab
2024-05-07 12:05 ` dpdklab
2024-05-07 12:05 ` dpdklab
2024-05-07 12:05 ` dpdklab
2024-05-07 12:05 ` dpdklab
2024-05-07 12:06 ` dpdklab
2024-05-07 12:06 ` dpdklab
2024-05-07 12:06 ` dpdklab
2024-05-07 12:06 ` dpdklab
2024-05-07 12:07 ` dpdklab
2024-05-07 12:07 ` dpdklab
2024-05-07 12:07 ` dpdklab
2024-05-07 12:07 ` dpdklab
2024-05-07 12:08 ` dpdklab
2024-05-07 12:08 ` dpdklab
2024-05-07 12:08 ` dpdklab
2024-05-07 12:08 ` dpdklab
2024-05-07 12:09 ` dpdklab
2024-05-07 12:09 ` dpdklab
2024-05-07 12:10 ` dpdklab
2024-05-07 12:10 ` dpdklab
2024-05-07 12:11 ` dpdklab
2024-05-07 12:11 ` dpdklab
2024-05-07 12:11 ` dpdklab
2024-05-07 12:11 ` dpdklab
2024-05-07 12:12 ` dpdklab
2024-05-07 12:12 ` dpdklab
2024-05-07 12:13 ` dpdklab
2024-05-07 12:13 ` dpdklab
2024-05-07 12:14 ` dpdklab
2024-05-07 12:15 ` dpdklab
2024-05-07 12:16 ` dpdklab
2024-05-07 12:17 ` dpdklab
2024-05-07 12:17 ` dpdklab
2024-05-07 12:18 ` dpdklab
2024-05-07 12:19 ` dpdklab
2024-05-07 12:20 ` dpdklab
2024-05-07 12:22 ` dpdklab
2024-05-07 12:24 ` |SUCCESS| pw139963 [PATCH 2/2] maintainers: update for crypto performance 0-day Robot
2024-05-07 12:25 ` |SUCCESS| pw139962-139963 [PATCH] [2/2] maintainers: update for cryp dpdklab
2024-05-07 12:25 ` dpdklab
2024-05-07 12:25 ` dpdklab
2024-05-07 12:26 ` dpdklab
2024-05-07 12:26 ` dpdklab
2024-05-07 12:26 ` dpdklab
2024-05-07 12:28 ` dpdklab
2024-05-07 12:28 ` dpdklab
2024-05-07 12:31 ` dpdklab
2024-05-07 12:32 ` dpdklab
2024-05-07 12:32 ` dpdklab
2024-05-07 12:34 ` dpdklab
2024-05-07 12:36 ` dpdklab
2024-05-07 12:36 ` dpdklab
2024-05-07 12:39 ` dpdklab
2024-05-07 12:40 ` dpdklab
2024-05-07 12:40 ` dpdklab
2024-05-07 12:45 ` dpdklab
2024-05-07 12:46 ` dpdklab
2024-05-07 12:47 ` dpdklab
2024-05-07 12:49 ` dpdklab
2024-05-07 12:52 ` dpdklab
2024-05-07 12:54 ` dpdklab
2024-05-07 12:57 ` dpdklab
2024-05-07 12:58 ` dpdklab
2024-05-07 13:02 ` dpdklab
2024-05-07 13:02 ` dpdklab
2024-05-07 13:14 ` dpdklab
2024-05-07 14:40 ` dpdklab
2024-05-07 18:36 ` 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=202405071059.447Ax9231917265@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).