From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121502-121504 [PATCH 3/3] app/crypto-perf: fix IPsec direction
Date: Mon, 2 Jan 2023 19:39:53 +0800 [thread overview]
Message-ID: <202301021139.302BdrkJ1757233@localhost.localdomain> (raw)
In-Reply-To: <20230102114655.300-3-anoobj@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121504
_Compilation OK_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Mon, 2 Jan 2023 17:16:53 +0530
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: c581c49cd3fcaff596fbe566e270b442e6326c79
121502-121504 --> 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:[~2023-01-02 11:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230102114655.300-3-anoobj@marvell.com>
2023-01-02 11:39 ` qemudev [this message]
2023-01-02 11:43 ` qemudev
2023-01-02 11:47 ` |SUCCESS| pw121504 " checkpatch
2023-01-02 12:39 ` 0-day Robot
2023-01-02 12:18 |SUCCESS| pw121502-121504 [PATCH] [3/3] " dpdklab
2023-01-02 12:23 dpdklab
2023-01-02 12:28 dpdklab
2023-01-02 12:32 dpdklab
2023-01-02 12:35 dpdklab
2023-01-02 12:39 dpdklab
2023-01-02 12:57 dpdklab
2023-01-02 13:16 dpdklab
2023-01-02 13:16 dpdklab
2023-01-02 13:32 dpdklab
2023-01-02 13:32 dpdklab
2023-01-02 13:36 dpdklab
2023-01-02 13:37 dpdklab
2023-01-02 13:39 dpdklab
2023-01-02 13:40 dpdklab
2023-01-02 13:40 dpdklab
2023-01-02 13:41 dpdklab
2023-01-02 13:44 dpdklab
2023-01-02 13:49 dpdklab
2023-01-02 13:50 dpdklab
2023-01-02 13:52 dpdklab
2023-01-02 13:52 dpdklab
2023-01-02 13: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=202301021139.302BdrkJ1757233@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).