From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137425 [PATCH v1] eventdev/crypto: fix enqueueing invalid ops
Date: Wed, 28 Feb 2024 18:21:05 +0800 [thread overview]
Message-ID: <202402281021.41SAL5eM957336@localhost.localdomain> (raw)
In-Reply-To: <20240228103919.2018017-1-ganapati.kundapura@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137425
_Compilation OK_
Submitter: Ganapati Kundapura <ganapati.kundapura@intel.com>
Date: Wed, 28 Feb 2024 04:39:19 -0600
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: 29cba188385e8c961bfb21690d0eda36f50277e1
137425 --> 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-28 10:45 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240228103919.2018017-1-ganapati.kundapura@intel.com>
2024-02-28 10:21 ` qemudev [this message]
2024-02-28 10:25 ` qemudev
2024-02-28 10:39 ` checkpatch
2024-02-28 11:45 ` 0-day Robot
2024-02-28 13:41 ` |SUCCESS| pw137425 [PATCH] [v1] eventdev/crypto: fix enqueueing inva dpdklab
2024-02-28 13:43 ` dpdklab
2024-02-28 13:44 ` dpdklab
2024-02-28 13:45 ` dpdklab
2024-02-28 13:51 ` dpdklab
2024-02-28 14:09 ` dpdklab
2024-02-28 14:09 ` dpdklab
2024-02-28 14:09 ` dpdklab
2024-02-28 14:10 ` dpdklab
2024-02-28 14:10 ` dpdklab
2024-02-28 14:29 ` dpdklab
2024-02-28 14:30 ` dpdklab
2024-02-28 14:33 ` dpdklab
2024-02-28 14:33 ` dpdklab
2024-02-28 14:34 ` dpdklab
2024-02-28 14:35 ` dpdklab
2024-02-28 14:42 ` dpdklab
2024-02-28 14:42 ` dpdklab
2024-02-28 14:42 ` dpdklab
2024-02-28 14:44 ` dpdklab
2024-02-28 14:44 ` dpdklab
2024-02-28 14:45 ` dpdklab
2024-02-28 14:45 ` dpdklab
2024-02-28 14:45 ` dpdklab
2024-02-28 14:46 ` dpdklab
2024-02-28 14:46 ` dpdklab
2024-02-28 14:46 ` dpdklab
2024-02-28 14:46 ` dpdklab
2024-02-28 14:46 ` dpdklab
2024-02-28 14:46 ` dpdklab
2024-02-28 14:47 ` dpdklab
2024-02-28 14:47 ` dpdklab
2024-02-28 14:47 ` dpdklab
2024-02-28 14:47 ` dpdklab
2024-02-28 14:48 ` dpdklab
2024-02-28 14:48 ` dpdklab
2024-02-28 14:48 ` dpdklab
2024-02-28 14:48 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:50 ` dpdklab
2024-02-28 14:50 ` dpdklab
2024-02-28 14:50 ` dpdklab
2024-02-28 14:51 ` dpdklab
2024-02-28 14:51 ` dpdklab
2024-02-28 14:51 ` dpdklab
2024-02-28 14:52 ` dpdklab
2024-02-28 14:52 ` dpdklab
2024-02-28 14:52 ` dpdklab
2024-02-28 14:52 ` dpdklab
2024-02-28 14:53 ` dpdklab
2024-02-28 14:54 ` dpdklab
2024-02-28 14:54 ` dpdklab
2024-02-28 15:17 ` dpdklab
2024-02-28 15:20 ` dpdklab
2024-02-28 16:10 ` dpdklab
2024-02-28 18:16 ` dpdklab
2024-02-28 20:09 ` dpdklab
2024-02-28 20:17 ` dpdklab
2024-02-29 11:36 ` dpdklab
2024-02-29 23:04 ` dpdklab
2024-02-29 23:06 ` dpdklab
2024-02-29 23:08 ` dpdklab
2024-02-29 23:13 ` dpdklab
2024-03-01 20:09 ` dpdklab
2024-03-01 21:03 ` dpdklab
2024-03-01 21:34 ` 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=202402281021.41SAL5eM957336@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).