From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124687 [PATCH] event/cnxk: fix SSO return code at fini
Date: Mon, 6 Mar 2023 15:23:30 +0800 [thread overview]
Message-ID: <202303060723.3267NU8Y3958389@localhost.localdomain> (raw)
In-Reply-To: <20230302105832.3955684-1-vfialko@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124687
_Compilation OK_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Thu, 2 Mar 2023 11:58:32 +0100
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: ca88db3ae76d878a8febe3fe1effe0b677403845
124687 --> 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:[~2023-03-06 7:37 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230302105832.3955684-1-vfialko@marvell.com>
2023-03-02 11:02 ` checkpatch
2023-03-02 12:59 ` 0-day Robot
2023-03-06 7:23 ` qemudev [this message]
2023-03-06 7:24 ` qemudev
2023-03-02 12:07 dpdklab
2023-03-02 12:08 dpdklab
2023-03-02 12:09 dpdklab
2023-03-02 12:11 dpdklab
2023-03-02 12:11 dpdklab
2023-03-02 12:15 dpdklab
2023-03-02 12:16 dpdklab
2023-03-02 12:19 dpdklab
2023-03-02 12:19 dpdklab
2023-03-02 12:24 dpdklab
2023-03-02 12:25 dpdklab
2023-03-02 12:28 dpdklab
2023-03-02 12:29 dpdklab
2023-03-02 12:31 dpdklab
2023-03-02 12:34 dpdklab
2023-03-02 12:36 dpdklab
2023-03-02 12:38 dpdklab
2023-03-02 12:41 dpdklab
2023-03-02 12:54 dpdklab
2023-03-02 13:03 dpdklab
2023-03-02 13:13 dpdklab
2023-03-02 13:15 dpdklab
2023-03-02 13:18 dpdklab
2023-03-02 13:35 dpdklab
2023-03-02 13:48 dpdklab
2023-03-02 21:16 dpdklab
2023-03-02 22:58 dpdklab
2023-03-03 2:29 dpdklab
2023-03-03 3:14 dpdklab
2023-03-04 3:51 dpdklab
2023-03-04 3:56 dpdklab
2023-03-04 4:06 dpdklab
2023-03-04 4:15 dpdklab
2023-03-04 4:31 dpdklab
2023-03-04 4:32 dpdklab
2023-03-04 4:40 dpdklab
2023-03-04 4:46 dpdklab
2023-03-04 4:49 dpdklab
2023-03-04 4:50 dpdklab
2023-03-04 4:51 dpdklab
2023-03-04 4:52 dpdklab
2023-03-04 4:53 dpdklab
2023-03-04 4:55 dpdklab
2023-03-04 4:59 dpdklab
2023-03-04 5:00 dpdklab
2023-03-04 5:01 dpdklab
2023-03-04 5:01 dpdklab
2023-03-04 5:01 dpdklab
2023-03-04 5:05 dpdklab
2023-03-04 5:08 dpdklab
2023-03-04 5:11 dpdklab
2023-03-04 5:11 dpdklab
2023-03-04 5:16 dpdklab
2023-03-04 5:17 dpdklab
2023-03-04 5:18 dpdklab
2023-03-04 5:48 dpdklab
2023-03-04 5:49 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=202303060723.3267NU8Y3958389@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).