From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126243 [PATCH] crypto/ipsec_mb: enqueue counter fix
Date: Tue, 18 Apr 2023 22:12:05 +0800 [thread overview]
Message-ID: <202304181412.33IEC57u4127781@localhost.localdomain> (raw)
In-Reply-To: <20230418142249.38447-1-saoirse.odonovan@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126243
_Compilation OK_
Submitter: Saoirse O'Donovan <saoirse.odonovan@intel.com>
Date: Tue, 18 Apr 2023 14:22:49 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 189c02f5ec891ed02927062e124e8ca03adf74e7
126243 --> 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-04-18 14:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230418142249.38447-1-saoirse.odonovan@intel.com>
2023-04-18 14:12 ` qemudev [this message]
2023-04-18 14:16 ` qemudev
2023-04-18 14:24 ` checkpatch
2023-04-18 17:39 ` 0-day Robot
2023-04-18 20:54 dpdklab
2023-04-18 20:56 dpdklab
2023-04-18 20:57 dpdklab
2023-04-18 21:02 dpdklab
2023-04-18 21:02 dpdklab
2023-04-18 21:03 dpdklab
2023-04-18 21:03 dpdklab
2023-04-18 21:04 dpdklab
2023-04-18 21:10 dpdklab
2023-04-18 21:11 dpdklab
2023-04-18 21:15 dpdklab
2023-04-18 21:20 dpdklab
2023-04-18 21:23 dpdklab
2023-04-18 21:31 dpdklab
2023-04-18 21:54 dpdklab
2023-04-18 21:54 dpdklab
2023-04-18 21:55 dpdklab
2023-04-18 21:59 dpdklab
2023-04-18 22:03 dpdklab
2023-04-18 22:15 dpdklab
2023-04-18 22:16 dpdklab
2023-04-18 22:17 dpdklab
2023-04-18 22:22 dpdklab
2023-04-19 7:12 dpdklab
2023-04-19 9:35 dpdklab
2023-04-19 12:17 dpdklab
2023-04-19 12:17 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=202304181412.33IEC57u4127781@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).