From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123696-123698 [PATCH v6 3/3] eventdev/crypto: add params set/get APIs
Date: Sat, 11 Feb 2023 01:32:10 +0800 [thread overview]
Message-ID: <202302101732.31AHWAS11913039@localhost.localdomain> (raw)
In-Reply-To: <20230210173744.3597666-3-s.v.naga.harish.k@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123698
_Compilation OK_
Submitter: Naga Harish K, S V <s.v.naga.harish.k@intel.com>
Date: Fri, 10 Feb 2023 11:37:42 -0600
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: 37e062b4955c898d2e7b8fdca27f4f6961b721e6
123696-123698 --> 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-02-10 17:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230210173744.3597666-3-s.v.naga.harish.k@intel.com>
2023-02-10 17:32 ` qemudev [this message]
2023-02-10 17:36 ` qemudev
2023-02-10 17:40 ` |SUCCESS| pw123698 " checkpatch
2023-02-10 18:02 |SUCCESS| pw123696-123698 [PATCH] [v6, " dpdklab
2023-02-10 18:06 dpdklab
2023-02-10 18:08 dpdklab
2023-02-10 18:09 dpdklab
2023-02-10 18:11 dpdklab
2023-02-10 18:12 dpdklab
2023-02-10 18:12 dpdklab
2023-02-10 18:14 dpdklab
2023-02-10 18:16 dpdklab
2023-02-10 18:18 dpdklab
2023-02-10 18:21 dpdklab
2023-02-10 18:24 dpdklab
2023-02-10 18:30 dpdklab
2023-02-10 20:19 dpdklab
2023-02-12 21:49 dpdklab
2023-02-12 22:19 dpdklab
2023-02-13 0:06 dpdklab
2023-02-14 9:10 dpdklab
2023-02-15 8:57 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=202302101732.31AHWAS11913039@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).