From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126919 [PATCH v2] doc: updated libcrypto dependencies in QAT guide
Date: Wed, 17 May 2023 19:22:44 +0800 [thread overview]
Message-ID: <202305171122.34HBMisZ1645705@localhost.localdomain> (raw)
In-Reply-To: <20230516132006.577354-1-samina.arshad@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126919
_Compilation OK_
Submitter: Samina Arshad <samina.arshad@intel.com>
Date: Tue, 16 May 2023 13:20:06 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: b795985685a0848e03716f81c7ccd3b61a075f95
126919 --> 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-05-17 11:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230516132006.577354-1-samina.arshad@intel.com>
2023-05-17 11:22 ` qemudev [this message]
2023-05-17 11:26 ` qemudev
2023-05-17 11:34 ` checkpatch
2023-05-17 15:36 |SUCCESS| pw126919 [PATCH] [v2] " dpdklab
2023-05-17 15:37 dpdklab
2023-05-17 15:40 dpdklab
2023-05-17 15:40 dpdklab
2023-05-17 15:41 dpdklab
2023-05-17 15:42 dpdklab
2023-05-17 15:48 dpdklab
2023-05-17 15:49 dpdklab
2023-05-17 15:51 dpdklab
2023-05-17 15:56 dpdklab
2023-05-17 16:00 dpdklab
2023-05-17 16:01 dpdklab
2023-05-17 16:06 dpdklab
2023-05-17 16:29 dpdklab
2023-05-17 16:50 dpdklab
2023-05-17 17:03 dpdklab
2023-05-17 17:04 dpdklab
2023-05-17 17:08 dpdklab
2023-05-17 17:11 dpdklab
2023-05-17 17:18 dpdklab
2023-05-17 17:18 dpdklab
2023-05-17 17:19 dpdklab
2023-05-17 17:23 dpdklab
2023-05-17 17:39 dpdklab
2023-05-17 19:22 dpdklab
2023-05-17 21:21 dpdklab
2023-05-17 21:58 dpdklab
2023-05-17 22:00 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=202305171122.34HBMisZ1645705@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).