From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138649-138651 [PATCH v7 4/4] cryptodev: remove rte marker fields
Date: Thu, 21 Mar 2024 05:39:22 +0800 [thread overview]
Message-ID: <202403202139.42KLdMW2384119@localhost.localdomain> (raw)
In-Reply-To: <1710972098-2209-5-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138651
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wed, 20 Mar 2024 15:01:35 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138649-138651 --> 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-20 22:05 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1710972098-2209-5-git-send-email-roretzla@linux.microsoft.com>
2024-03-20 21:39 ` qemudev [this message]
2024-03-20 21:43 ` qemudev
2024-03-20 22:03 ` |SUCCESS| pw138651 " checkpatch
2024-03-20 23:05 ` |FAILURE| " 0-day Robot
2024-03-21 0:17 ` |SUCCESS| pw138649-138651 [PATCH] [v7,4/4] cryptodev: remove rte mar dpdklab
2024-03-21 0:18 ` dpdklab
2024-03-21 0:25 ` dpdklab
2024-03-21 0:34 ` dpdklab
2024-03-21 0:36 ` dpdklab
2024-03-21 0:36 ` dpdklab
2024-03-21 0:37 ` dpdklab
2024-03-21 0:42 ` dpdklab
2024-03-21 0:44 ` dpdklab
2024-03-21 0:45 ` dpdklab
2024-03-21 0:48 ` dpdklab
2024-03-21 0:50 ` |WARNING| " dpdklab
2024-03-21 0:50 ` dpdklab
2024-03-21 0:52 ` dpdklab
2024-03-21 0:52 ` |SUCCESS| " dpdklab
2024-03-21 0:52 ` |WARNING| " dpdklab
2024-03-21 1:01 ` dpdklab
2024-03-21 1:03 ` dpdklab
2024-03-21 1:08 ` dpdklab
2024-03-21 1:13 ` |SUCCESS| " dpdklab
2024-03-21 1:13 ` |WARNING| " dpdklab
2024-03-21 1:18 ` dpdklab
2024-03-21 1:44 ` dpdklab
2024-03-21 1:47 ` |SUCCESS| " dpdklab
2024-03-21 1:48 ` dpdklab
2024-03-21 1:48 ` dpdklab
2024-03-21 1:49 ` dpdklab
2024-03-21 1:49 ` dpdklab
2024-03-21 1:52 ` dpdklab
2024-03-21 1:53 ` dpdklab
2024-03-21 1:55 ` dpdklab
2024-03-21 1:56 ` dpdklab
2024-03-21 2:24 ` dpdklab
2024-03-21 2:27 ` dpdklab
2024-03-21 2:29 ` dpdklab
2024-03-21 2:29 ` dpdklab
2024-03-21 2:29 ` dpdklab
2024-03-21 2:30 ` dpdklab
2024-03-21 2:30 ` dpdklab
2024-03-21 2:41 ` dpdklab
2024-03-21 2:42 ` dpdklab
2024-03-21 2:48 ` dpdklab
2024-03-21 2:51 ` dpdklab
2024-03-21 2:57 ` dpdklab
2024-03-21 2:58 ` dpdklab
2024-03-21 2:59 ` dpdklab
2024-03-21 2:59 ` dpdklab
2024-03-21 3:00 ` dpdklab
2024-03-21 3:01 ` dpdklab
2024-03-21 3:01 ` dpdklab
2024-03-21 3:02 ` dpdklab
2024-03-21 3:03 ` dpdklab
2024-03-21 3:03 ` dpdklab
2024-03-21 3:03 ` dpdklab
2024-03-21 3:04 ` dpdklab
2024-03-21 3:05 ` dpdklab
2024-03-21 3:05 ` dpdklab
2024-03-21 3:06 ` dpdklab
2024-03-21 3:06 ` dpdklab
2024-03-21 3:06 ` dpdklab
2024-03-21 3:07 ` dpdklab
2024-03-21 3:07 ` dpdklab
2024-03-21 3:08 ` dpdklab
2024-03-21 3:09 ` dpdklab
2024-03-21 3:09 ` dpdklab
2024-03-21 3:10 ` dpdklab
2024-03-21 3:10 ` dpdklab
2024-03-21 3:20 ` dpdklab
2024-03-21 3:21 ` dpdklab
2024-03-21 3:24 ` dpdklab
2024-03-21 3:27 ` dpdklab
2024-03-21 3:43 ` dpdklab
2024-03-21 4:55 ` dpdklab
2024-03-21 5:44 ` dpdklab
2024-03-21 16:18 ` dpdklab
2024-03-22 14:23 ` dpdklab
2024-03-22 14:59 ` 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=202403202139.42KLdMW2384119@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).