From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126080 [PATCH] crypto/scheduler: fix last element for valid args
Date: Fri, 14 Apr 2023 20:22:14 +0800 [thread overview]
Message-ID: <202304141222.33ECMEla1319657@localhost.localdomain> (raw)
In-Reply-To: <20230414123306.575977-1-ciara.power@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126080
_Compilation OK_
Submitter: Ciara Power <ciara.power@intel.com>
Date: Fri, 14 Apr 2023 12:33:06 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 189c02f5ec891ed02927062e124e8ca03adf74e7
126080 --> 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-14 12:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230414123306.575977-1-ciara.power@intel.com>
2023-04-14 12:22 ` qemudev [this message]
2023-04-14 12:26 ` qemudev
2023-04-14 12:33 ` checkpatch
2023-04-14 13:39 ` 0-day Robot
2023-04-14 18:47 dpdklab
2023-04-14 18:49 dpdklab
2023-04-14 18:49 dpdklab
2023-04-14 18:54 dpdklab
2023-04-14 18:57 dpdklab
2023-04-14 18:58 dpdklab
2023-04-14 18:58 dpdklab
2023-04-14 19:02 dpdklab
2023-04-14 19:10 dpdklab
2023-04-14 19:18 dpdklab
2023-04-14 20:00 dpdklab
2023-04-14 20:14 dpdklab
2023-04-14 20:58 dpdklab
2023-04-14 21:02 dpdklab
2023-04-14 21:07 dpdklab
2023-04-14 21:07 dpdklab
2023-04-14 21:10 dpdklab
2023-04-14 21:11 dpdklab
2023-04-14 21:13 dpdklab
2023-04-14 21:26 dpdklab
2023-04-14 21:26 dpdklab
2023-04-14 21:28 dpdklab
2023-04-14 21:31 dpdklab
2023-04-15 1:11 dpdklab
2023-04-15 4:00 dpdklab
2023-04-15 4:21 dpdklab
2023-04-15 4:25 dpdklab
2023-04-15 4:33 dpdklab
2023-04-15 8:31 dpdklab
2023-04-15 8: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=202304141222.33ECMEla1319657@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).