From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122682 [PATCH] test/crypto: fix typo in AES test
Date: Mon, 30 Jan 2023 19:58:02 +0800 [thread overview]
Message-ID: <202301301158.30UBw2HE2695723@localhost.localdomain> (raw)
In-Reply-To: <20230130120303.793537-1-vikash.chandrax.poddar@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122682
_Compilation OK_
Submitter: Vikash Poddar <vikash.chandrax.poddar@intel.com>
Date: Mon, 30 Jan 2023 12:03:03 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 1917fccc620c6d4fffe005418a48253710cfbb14
122682 --> 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-30 12:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230130120303.793537-1-vikash.chandrax.poddar@intel.com>
2023-01-30 11:58 ` qemudev [this message]
2023-01-30 12:01 ` qemudev
2023-01-30 12:06 ` |WARNING| " checkpatch
2023-01-30 12:59 ` |SUCCESS| " 0-day Robot
2023-01-30 16:25 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-30 15:41 dpdklab
2023-01-30 15:17 dpdklab
2023-01-30 15:11 dpdklab
2023-01-30 15:04 dpdklab
2023-01-30 15:03 dpdklab
2023-01-30 15:03 dpdklab
2023-01-30 15:03 dpdklab
2023-01-30 15:03 dpdklab
2023-01-30 15:03 dpdklab
2023-01-30 15:03 dpdklab
2023-01-30 15:02 dpdklab
2023-01-30 14:59 dpdklab
2023-01-30 12:50 dpdklab
2023-01-30 12:47 dpdklab
2023-01-30 12:37 dpdklab
2023-01-30 12:36 dpdklab
2023-01-30 12:31 dpdklab
2023-01-30 12:31 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=202301301158.30UBw2HE2695723@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).