From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120357 [PATCH v1] eventdev/crypto: add all failed events to circular buffer
Date: Wed, 30 Nov 2022 23:43:56 +0800 [thread overview]
Message-ID: <202211301543.2AUFhuKr3307148@localhost.localdomain> (raw)
In-Reply-To: <20221130154938.1698236-1-ganapati.kundapura@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/120357
_Compilation OK_
Submitter: Ganapati Kundapura <ganapati.kundapura@intel.com>
Date: Wed, 30 Nov 2022 09:49:38 -0600
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: f262f16087ea6a77357a915cf4c0d10ddc7b6562
120357 --> 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:[~2022-11-30 15:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221130154938.1698236-1-ganapati.kundapura@intel.com>
2022-11-30 15:43 ` qemudev [this message]
2022-11-30 15:47 ` qemudev
2022-11-30 15:50 ` checkpatch
2022-11-30 16:58 ` 0-day Robot
2022-11-30 16:20 |SUCCESS| pw120357 [PATCH] [v1] " dpdklab
2022-11-30 16:32 dpdklab
2022-11-30 16:58 dpdklab
2022-11-30 17:02 dpdklab
2022-11-30 17:05 dpdklab
2022-11-30 17:22 dpdklab
2022-11-30 17:49 dpdklab
2022-11-30 18:21 dpdklab
2022-12-02 9:16 dpdklab
2022-12-02 9:31 dpdklab
2022-12-02 9:56 dpdklab
2022-12-02 10:22 dpdklab
2022-12-02 10:50 dpdklab
2022-12-02 11:15 dpdklab
2022-12-02 11:46 dpdklab
2022-12-02 12:11 dpdklab
2022-12-02 12:21 dpdklab
2022-12-02 12:35 dpdklab
2022-12-02 13:03 dpdklab
2022-12-02 13:34 dpdklab
2022-12-02 13:34 dpdklab
2022-12-03 4:03 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=202211301543.2AUFhuKr3307148@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).