From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120517-120521 [PATCH v3 5/5] eventdev/crypto: fix failed events
Date: Sat, 10 Dec 2022 08:40:09 +0800 [thread overview]
Message-ID: <202212100040.2BA0e9fb1020884@localhost.localdomain> (raw)
In-Reply-To: <20221207064945.1665368-5-ganapati.kundapura@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/120521
_Compilation OK_
Submitter: Ganapati Kundapura <ganapati.kundapura@intel.com>
Date: Wed, 7 Dec 2022 00:49:41 -0600
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: f262f16087ea6a77357a915cf4c0d10ddc7b6562
120517-120521 --> 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 prev parent reply other threads:[~2022-12-10 0:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221207064945.1665368-5-ganapati.kundapura@intel.com>
2022-12-07 6:51 ` |SUCCESS| pw120521 " checkpatch
2022-12-07 8:38 ` 0-day Robot
2022-12-08 16:15 ` |SUCCESS| pw120517-120521 " qemudev
2022-12-08 16:15 ` qemudev
2022-12-08 16:51 ` qemudev
2022-12-08 16:51 ` qemudev
2022-12-10 0:40 ` qemudev [this message]
2022-12-10 0:40 ` qemudev
2022-12-07 8:49 |SUCCESS| pw120517-120521 [PATCH] [v3, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2022-12-07 8:23 dpdklab
2022-12-07 8:23 dpdklab
2022-12-07 8:22 dpdklab
2022-12-07 8:19 dpdklab
2022-12-07 8:16 dpdklab
2022-12-07 8:11 dpdklab
2022-12-07 8:10 dpdklab
2022-12-07 8:06 dpdklab
2022-12-07 8:01 dpdklab
2022-12-07 7:59 dpdklab
2022-12-07 7:45 dpdklab
2022-12-07 7:40 dpdklab
2022-12-07 7:40 dpdklab
2022-12-07 7:35 dpdklab
2022-12-07 7:33 dpdklab
2022-12-07 7:28 dpdklab
2022-12-07 7:26 dpdklab
2022-12-07 7:19 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=202212100040.2BA0e9fb1020884@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).