From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138873-138875 [PATCH v8 4/4] cryptodev: remove rte marker fields
Date: Thu, 28 Mar 2024 03:35:03 +0800 [thread overview]
Message-ID: <202403271935.42RJZ3PW3773998@localhost.localdomain> (raw)
In-Reply-To: <1711569406-7750-5-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138875
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wed, 27 Mar 2024 12:56:43 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: ded4d4765171b88470e59307f10625e942f22fca
138873-138875 --> 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-03-27 19:59 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1711569406-7750-5-git-send-email-roretzla@linux.microsoft.com>
2024-03-27 19:35 ` qemudev [this message]
2024-03-27 19:39 ` qemudev
2024-03-27 19:57 ` |SUCCESS| pw138875 " checkpatch
2024-03-27 20:35 ` |SUCCESS| pw138873-138875 [PATCH] [v8,4/4] cryptodev: remove rte mar dpdklab
2024-03-27 20:35 ` dpdklab
2024-03-27 20:35 ` dpdklab
2024-03-27 20:35 ` dpdklab
2024-03-27 20:36 ` dpdklab
2024-03-27 20:36 ` dpdklab
2024-03-27 20:36 ` dpdklab
2024-03-27 20:36 ` dpdklab
2024-03-27 20:37 ` dpdklab
2024-03-27 20:37 ` dpdklab
2024-03-27 20:38 ` dpdklab
2024-03-27 20:40 ` |WARNING| " dpdklab
2024-03-27 20:42 ` dpdklab
2024-03-27 20:43 ` |SUCCESS| " dpdklab
2024-03-27 20:44 ` dpdklab
2024-03-27 20:44 ` |WARNING| " dpdklab
2024-03-27 20:44 ` dpdklab
2024-03-27 20:45 ` |FAILURE| pw138875 [PATCH v8 4/4] cryptodev: remove rte marker fields 0-day Robot
2024-03-27 20:45 ` |SUCCESS| pw138873-138875 [PATCH] [v8,4/4] cryptodev: remove rte mar dpdklab
2024-03-27 20:46 ` |WARNING| " dpdklab
2024-03-27 20:47 ` dpdklab
2024-03-27 20:48 ` dpdklab
2024-03-27 20:49 ` |SUCCESS| " dpdklab
2024-03-27 20:52 ` |WARNING| " dpdklab
2024-03-27 20:53 ` dpdklab
2024-03-27 20:56 ` |SUCCESS| " dpdklab
2024-03-27 20:57 ` dpdklab
2024-03-27 20:57 ` dpdklab
2024-03-27 20:57 ` dpdklab
2024-03-27 20:59 ` dpdklab
2024-03-27 21:00 ` dpdklab
2024-03-27 21:01 ` dpdklab
2024-03-27 21:01 ` dpdklab
2024-03-27 21:03 ` dpdklab
2024-03-27 21:05 ` dpdklab
2024-03-27 21:06 ` dpdklab
2024-03-27 21:06 ` dpdklab
2024-03-27 21:08 ` dpdklab
2024-03-27 21:09 ` dpdklab
2024-03-27 21:09 ` dpdklab
2024-03-27 21:10 ` dpdklab
2024-03-27 21:12 ` dpdklab
2024-03-27 21:12 ` dpdklab
2024-03-27 21:13 ` dpdklab
2024-03-27 21:13 ` dpdklab
2024-03-27 21:16 ` dpdklab
2024-03-27 21:16 ` dpdklab
2024-03-27 21:22 ` dpdklab
2024-03-27 21:24 ` dpdklab
2024-03-27 21:25 ` dpdklab
2024-03-27 21:27 ` dpdklab
2024-03-27 21:29 ` dpdklab
2024-03-27 21:29 ` dpdklab
2024-03-27 21:30 ` dpdklab
2024-03-27 21:30 ` dpdklab
2024-03-27 21:31 ` dpdklab
2024-03-27 21:31 ` dpdklab
2024-03-27 21:34 ` dpdklab
2024-03-27 21:38 ` dpdklab
2024-03-27 21:38 ` dpdklab
2024-03-27 21:39 ` dpdklab
2024-03-27 21:42 ` dpdklab
2024-03-27 21:42 ` dpdklab
2024-03-27 21:49 ` dpdklab
2024-03-27 21:49 ` dpdklab
2024-03-27 21:52 ` dpdklab
2024-03-27 21:58 ` dpdklab
2024-03-27 22:01 ` dpdklab
2024-03-27 22:02 ` dpdklab
2024-03-27 22:08 ` dpdklab
2024-03-27 22:19 ` dpdklab
2024-03-27 22:21 ` dpdklab
2024-03-27 22:30 ` dpdklab
2024-03-27 22:46 ` dpdklab
2024-03-27 22:58 ` dpdklab
2024-03-27 23:24 ` dpdklab
2024-03-27 23:26 ` dpdklab
2024-03-27 23:28 ` dpdklab
2024-03-27 23:50 ` dpdklab
2024-03-27 23:50 ` dpdklab
2024-03-28 0:06 ` dpdklab
2024-04-02 11:20 ` dpdklab
2024-04-02 11:24 ` dpdklab
2024-04-02 11:28 ` dpdklab
2024-04-02 11:32 ` dpdklab
2024-04-02 11:51 ` 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=202403271935.42RJZ3PW3773998@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).