From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126893-126900 [PATCH v2 8/8] crypto/ipsec_mb: set and use session ID
Date: Wed, 17 May 2023 11:07:14 +0800 [thread overview]
Message-ID: <202305170307.34H37Ede955049@localhost.localdomain> (raw)
In-Reply-To: <20230516152422.606617-9-ciara.power@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126900
_Compilation OK_
Submitter: Ciara Power <ciara.power@intel.com>
Date: Tue, 16 May 2023 15:24:15 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: b795985685a0848e03716f81c7ccd3b61a075f95
126893-126900 --> 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-17 3:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230516152422.606617-9-ciara.power@intel.com>
2023-05-16 15:25 ` |SUCCESS| pw126900 " checkpatch
2023-05-16 16:20 ` 0-day Robot
2023-05-17 3:07 ` qemudev [this message]
2023-05-17 3:07 ` |SUCCESS| pw126893-126900 " qemudev
2023-05-17 2:14 |SUCCESS| pw126893-126900 [PATCH] [v2, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-05-17 2:10 dpdklab
2023-05-17 2:00 dpdklab
2023-05-17 1:56 dpdklab
2023-05-17 1:41 dpdklab
2023-05-16 21:05 dpdklab
2023-05-16 21:05 dpdklab
2023-05-16 18:30 dpdklab
2023-05-16 18:06 dpdklab
2023-05-16 18:02 dpdklab
2023-05-16 17:37 dpdklab
2023-05-16 17:31 dpdklab
2023-05-16 17:25 dpdklab
2023-05-16 17:18 dpdklab
2023-05-16 17:17 dpdklab
2023-05-16 17:16 dpdklab
2023-05-16 17:15 dpdklab
2023-05-16 17:12 dpdklab
2023-05-16 17:10 dpdklab
2023-05-16 17:00 dpdklab
2023-05-16 16:52 dpdklab
2023-05-16 16:46 dpdklab
2023-05-16 16:42 dpdklab
2023-05-16 16:40 dpdklab
2023-05-16 16:34 dpdklab
2023-05-16 16:33 dpdklab
2023-05-16 16:33 dpdklab
2023-05-16 16:32 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=202305170307.34H37Ede955049@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).