From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143674-143675 [PATCH 2/2] crypto/qat: fix thread-safety issue in the crc
Date: Thu, 5 Sep 2024 22:45:17 +0800 [thread overview]
Message-ID: <202409051445.485EjHYJ2059651@localhost.localdomain> (raw)
In-Reply-To: <20240905150722.27789-2-arkadiuszx.kusztal@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143675
_Compilation OK_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Thu, 5 Sep 2024 16:07:21 +0100
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: b3485f4293997d35b6daecc3437bb0c183a51fb3
143674-143675 --> 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:[~2024-09-05 15:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240905150722.27789-2-arkadiuszx.kusztal@intel.com>
2024-09-05 14:45 ` qemudev [this message]
2024-09-05 14:49 ` qemudev
2024-09-05 15:08 ` |SUCCESS| pw143675 " checkpatch
2024-09-05 16:04 ` 0-day Robot
2024-09-05 19:56 ` |SUCCESS| pw143674-143675 [PATCH] [2/2] crypto/qat: fix thread-safet dpdklab
2024-09-05 20:40 ` dpdklab
2024-09-05 22:04 ` dpdklab
2024-09-05 22:16 ` dpdklab
2024-09-05 22:22 ` dpdklab
2024-09-05 22:32 ` dpdklab
2024-09-05 22:39 ` dpdklab
2024-09-05 22:40 ` dpdklab
2024-09-05 22:41 ` dpdklab
2024-09-05 22:43 ` dpdklab
2024-09-05 22:44 ` dpdklab
2024-09-05 22:49 ` |PENDING| " dpdklab
2024-09-05 22:56 ` dpdklab
2024-09-05 23:30 ` |SUCCESS| " dpdklab
2024-09-06 3:48 ` dpdklab
2024-09-06 4:02 ` dpdklab
2024-09-06 4:04 ` dpdklab
2024-09-06 6:32 ` dpdklab
2024-09-06 6:34 ` dpdklab
2024-09-06 6:39 ` dpdklab
2024-09-07 3:48 ` dpdklab
2024-09-17 21:41 ` dpdklab
2024-09-17 22:02 ` 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=202409051445.485EjHYJ2059651@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).