From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126838 [PATCH] test/crypto: remove redundant code
Date: Fri, 12 May 2023 22:33:45 +0800 [thread overview]
Message-ID: <202305121433.34CEXjvC3686526@localhost.localdomain> (raw)
In-Reply-To: <20230512142148.262-1-anoobj@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126838
_Compilation OK_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Fri, 12 May 2023 19:51:48 +0530
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 4385ef167b066772187477918f645ddd94e3234b
126838 --> 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 prev parent reply other threads:[~2023-05-12 14:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230512142148.262-1-anoobj@marvell.com>
2023-05-12 14:22 ` checkpatch
2023-05-12 14:33 ` qemudev [this message]
2023-05-12 14:38 ` qemudev
2023-05-12 15:19 ` 0-day Robot
2023-05-12 16:52 dpdklab
2023-05-12 16:52 dpdklab
2023-05-12 16:57 dpdklab
2023-05-12 16:58 dpdklab
2023-05-12 16:58 dpdklab
2023-05-12 17:04 dpdklab
2023-05-12 17:05 dpdklab
2023-05-12 17:17 dpdklab
2023-05-12 17:41 dpdklab
2023-05-12 17:42 dpdklab
2023-05-12 17:49 dpdklab
2023-05-12 17:52 dpdklab
2023-05-12 17:52 dpdklab
2023-05-12 17:54 dpdklab
2023-05-12 17:56 dpdklab
2023-05-12 17:59 dpdklab
2023-05-12 18:02 dpdklab
2023-05-12 18:04 dpdklab
2023-05-12 18:16 dpdklab
2023-05-12 18:20 dpdklab
2023-05-12 18:20 dpdklab
2023-05-12 18:20 dpdklab
2023-05-12 19:20 dpdklab
2023-05-12 20:01 dpdklab
2023-05-12 20:23 dpdklab
2023-05-12 20:23 dpdklab
2023-05-13 1:38 dpdklab
2023-05-13 1:53 dpdklab
2023-05-13 2:01 dpdklab
2023-05-13 2:06 dpdklab
2023-05-13 2:10 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=202305121433.34CEXjvC3686526@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).