From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137466 [PATCH v4] common/qat: add virtual qat device (vQAT)
Date: Thu, 29 Feb 2024 18:04:56 +0800 [thread overview]
Message-ID: <202402291004.41TA4u8H1777266@localhost.localdomain> (raw)
In-Reply-To: <20240229102141.32527-1-arkadiuszx.kusztal@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137466
_Compilation OK_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Thu, 29 Feb 2024 10:21:41 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137466 --> 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-02-29 10:29 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229102141.32527-1-arkadiuszx.kusztal@intel.com>
2024-02-29 10:04 ` qemudev [this message]
2024-02-29 10:09 ` qemudev
2024-02-29 10:22 ` |SUCCESS| pw137466 [PATCH v4] common/qat: add virtual qat device vQAT checkpatch
2024-02-29 11:25 ` |SUCCESS| pw137466 [PATCH v4] common/qat: add virtual qat device (vQAT) 0-day Robot
2024-02-29 12:06 ` |SUCCESS| pw137466 [PATCH] [v4] common/qat: add virtual qat device ( dpdklab
2024-02-29 12:11 ` dpdklab
2024-02-29 12:12 ` dpdklab
2024-02-29 12:12 ` dpdklab
2024-02-29 12:13 ` dpdklab
2024-02-29 12:13 ` dpdklab
2024-02-29 12:30 ` dpdklab
2024-02-29 12:31 ` dpdklab
2024-02-29 12:31 ` dpdklab
2024-02-29 12:31 ` dpdklab
2024-02-29 12:32 ` dpdklab
2024-02-29 12:32 ` dpdklab
2024-02-29 12:32 ` dpdklab
2024-02-29 12:35 ` dpdklab
2024-02-29 12:35 ` dpdklab
2024-02-29 12:36 ` dpdklab
2024-02-29 12:36 ` dpdklab
2024-02-29 12:36 ` dpdklab
2024-02-29 12:37 ` dpdklab
2024-02-29 12:37 ` dpdklab
2024-02-29 12:37 ` dpdklab
2024-02-29 12:37 ` dpdklab
2024-02-29 12:38 ` dpdklab
2024-02-29 12:38 ` dpdklab
2024-02-29 12:38 ` dpdklab
2024-02-29 12:38 ` dpdklab
2024-02-29 12:39 ` dpdklab
2024-02-29 12:39 ` dpdklab
2024-02-29 12:40 ` dpdklab
2024-02-29 12:40 ` dpdklab
2024-02-29 12:40 ` dpdklab
2024-02-29 12:41 ` dpdklab
2024-02-29 12:41 ` dpdklab
2024-02-29 12:41 ` dpdklab
2024-02-29 12:41 ` dpdklab
2024-02-29 12:41 ` dpdklab
2024-02-29 12:42 ` dpdklab
2024-02-29 12:58 ` dpdklab
2024-02-29 12:58 ` dpdklab
2024-02-29 12:59 ` dpdklab
2024-02-29 13:00 ` dpdklab
2024-02-29 13:00 ` dpdklab
2024-02-29 13:01 ` dpdklab
2024-02-29 13:01 ` dpdklab
2024-02-29 13:01 ` dpdklab
2024-02-29 13:02 ` dpdklab
2024-02-29 13:02 ` dpdklab
2024-02-29 13:03 ` dpdklab
2024-02-29 13:04 ` dpdklab
2024-02-29 13:04 ` dpdklab
2024-02-29 13:04 ` dpdklab
2024-02-29 13:05 ` dpdklab
2024-02-29 13:05 ` dpdklab
2024-02-29 13:11 ` dpdklab
2024-02-29 13:16 ` dpdklab
2024-02-29 13:16 ` dpdklab
2024-02-29 13:17 ` dpdklab
2024-02-29 13:17 ` dpdklab
2024-02-29 13:17 ` dpdklab
2024-02-29 13:31 ` dpdklab
2024-02-29 13:31 ` dpdklab
2024-02-29 13:35 ` dpdklab
2024-02-29 13:44 ` dpdklab
2024-02-29 14:19 ` dpdklab
2024-03-01 5:24 ` dpdklab
2024-03-01 5:33 ` dpdklab
2024-03-01 5:34 ` dpdklab
2024-03-01 5:38 ` dpdklab
2024-03-02 4:32 ` dpdklab
2024-03-02 19:01 ` dpdklab
2024-03-02 19:28 ` dpdklab
2024-03-02 20:00 ` 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=202402291004.41TA4u8H1777266@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).