From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139086-139089 [PATCH v10 4/4] cryptodev: remove rte marker fields
Date: Thu, 4 Apr 2024 01:34:00 +0800 [thread overview]
Message-ID: <202404031734.433HY08r1901358@localhost.localdomain> (raw)
In-Reply-To: <1712166816-10624-5-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139089
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wed, 3 Apr 2024 10:53:33 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139086-139089 --> 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-04-03 17:58 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1712166816-10624-5-git-send-email-roretzla@linux.microsoft.com>
2024-04-03 17:34 ` qemudev [this message]
2024-04-03 17:38 ` qemudev
2024-04-03 17:54 ` |SUCCESS| pw139089 " checkpatch
2024-04-03 18:45 ` 0-day Robot
2024-04-04 0:04 ` |SUCCESS| pw139086-139089 [PATCH] [v10,4/4] cryptodev: remove rte ma dpdklab
2024-04-04 0:05 ` dpdklab
2024-04-04 0:40 ` dpdklab
2024-04-04 0:41 ` dpdklab
2024-04-04 0:43 ` dpdklab
2024-04-04 0:44 ` dpdklab
2024-04-04 0:45 ` dpdklab
2024-04-04 0:55 ` dpdklab
2024-04-04 0:59 ` dpdklab
2024-04-04 1:00 ` dpdklab
2024-04-04 1:01 ` |WARNING| " dpdklab
2024-04-04 1:02 ` |SUCCESS| " dpdklab
2024-04-04 1:03 ` |WARNING| " dpdklab
2024-04-04 1:04 ` |SUCCESS| " dpdklab
2024-04-04 1:05 ` |WARNING| " dpdklab
2024-04-04 1:06 ` dpdklab
2024-04-04 1:07 ` dpdklab
2024-04-04 1:09 ` dpdklab
2024-04-04 1:09 ` dpdklab
2024-04-04 1:10 ` dpdklab
2024-04-04 1:12 ` |SUCCESS| " dpdklab
2024-04-04 1:12 ` |WARNING| " dpdklab
2024-04-04 1:12 ` dpdklab
2024-04-04 1:13 ` dpdklab
2024-04-04 1:14 ` |SUCCESS| " dpdklab
2024-04-04 1:18 ` |WARNING| " dpdklab
2024-04-04 1:19 ` |SUCCESS| " dpdklab
2024-04-04 1:19 ` dpdklab
2024-04-04 1:19 ` dpdklab
2024-04-04 1:20 ` dpdklab
2024-04-04 1:20 ` dpdklab
2024-04-04 1:20 ` dpdklab
2024-04-04 1:20 ` dpdklab
2024-04-04 1:21 ` dpdklab
2024-04-04 1:22 ` dpdklab
2024-04-04 1:22 ` dpdklab
2024-04-04 1:22 ` dpdklab
2024-04-04 1:23 ` dpdklab
2024-04-04 1:23 ` dpdklab
2024-04-04 1:23 ` dpdklab
2024-04-04 1:23 ` dpdklab
2024-04-04 1:24 ` dpdklab
2024-04-04 1:25 ` dpdklab
2024-04-04 1:25 ` dpdklab
2024-04-04 1:25 ` dpdklab
2024-04-04 1:25 ` dpdklab
2024-04-04 1:25 ` dpdklab
2024-04-04 1:26 ` dpdklab
2024-04-04 1:26 ` dpdklab
2024-04-04 1:26 ` dpdklab
2024-04-04 1:27 ` dpdklab
2024-04-04 1:43 ` dpdklab
2024-04-04 1:43 ` dpdklab
2024-04-04 1:43 ` dpdklab
2024-04-04 1:44 ` dpdklab
2024-04-04 1:44 ` dpdklab
2024-04-04 1:44 ` dpdklab
2024-04-04 1:45 ` dpdklab
2024-04-04 1:46 ` dpdklab
2024-04-04 1:46 ` dpdklab
2024-04-04 1:47 ` dpdklab
2024-04-04 1:48 ` dpdklab
2024-04-04 1:48 ` dpdklab
2024-04-04 1:49 ` dpdklab
2024-04-04 1:50 ` dpdklab
2024-04-04 1:52 ` dpdklab
2024-04-04 1:56 ` dpdklab
2024-04-04 1:56 ` dpdklab
2024-04-04 1:57 ` dpdklab
2024-04-04 2:00 ` dpdklab
2024-04-04 2:01 ` dpdklab
2024-04-04 2:01 ` dpdklab
2024-04-04 2:03 ` dpdklab
2024-04-04 2:11 ` dpdklab
2024-04-04 2:26 ` dpdklab
2024-04-04 2:33 ` dpdklab
2024-04-04 2:34 ` dpdklab
2024-04-04 2:36 ` dpdklab
2024-04-04 2:37 ` dpdklab
2024-04-04 2:38 ` dpdklab
2024-04-04 2:49 ` dpdklab
2024-04-04 3:49 ` dpdklab
2024-04-04 12:59 ` dpdklab
2024-04-04 13:03 ` dpdklab
2024-04-04 13:07 ` dpdklab
2024-04-04 13:26 ` dpdklab
2024-04-04 13:30 ` 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=202404031734.433HY08r1901358@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).