From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122760 [PATCH] crypto/ipsec_mb: fix zuc256 maximum tag length
Date: Wed, 1 Feb 2023 01:11:57 +0800 [thread overview]
Message-ID: <202301311711.30VHBv7G232953@localhost.localdomain> (raw)
In-Reply-To: <20230131172027.524502-1-ciara.power@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122760
_Compilation OK_
Submitter: Ciara Power <ciara.power@intel.com>
Date: Tue, 31 Jan 2023 17:20:27 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: df7d2c6247837da3589b99e04a3269d89504bdd5
122760 --> 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-31 17:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230131172027.524502-1-ciara.power@intel.com>
2023-01-31 17:11 ` qemudev [this message]
2023-01-31 17:15 ` qemudev
2023-01-31 17:21 ` checkpatch
2023-01-31 18:39 ` 0-day Robot
2023-02-01 3:07 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-01 1:58 dpdklab
2023-02-01 1:50 dpdklab
2023-02-01 0:12 dpdklab
2023-02-01 0:12 dpdklab
2023-02-01 0:11 dpdklab
2023-02-01 0:11 dpdklab
2023-02-01 0:11 dpdklab
2023-02-01 0:11 dpdklab
2023-02-01 0:10 dpdklab
2023-01-31 23:37 dpdklab
2023-01-31 23:34 dpdklab
2023-01-31 23:20 dpdklab
2023-01-31 19:43 dpdklab
2023-01-31 18:12 dpdklab
2023-01-31 18:07 dpdklab
2023-01-31 18:05 dpdklab
2023-01-31 18:00 dpdklab
2023-01-31 17:57 dpdklab
2023-01-31 17:56 dpdklab
2023-01-31 17:52 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=202301311711.30VHBv7G232953@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).