From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125894-125895 [PATCH 2/2] event/cnxk: restrict stashing to multi-core
Date: Tue, 11 Apr 2023 14:52:11 +0800 [thread overview]
Message-ID: <202304110652.33B6qBqm3093537@localhost.localdomain> (raw)
In-Reply-To: <20230411070129.870-2-pbhagavatula@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125895
_Compilation OK_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Tue, 11 Apr 2023 12:31:28 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 65487b12db83c9ef37526a983c43191cd44dae99
125894-125895 --> 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:[~2023-04-11 7:06 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230411070129.870-2-pbhagavatula@marvell.com>
2023-04-11 6:52 ` qemudev [this message]
2023-04-11 6:56 ` qemudev
2023-04-11 7:03 ` |SUCCESS| pw125895 " checkpatch
2023-04-11 7:59 ` 0-day Robot
2023-04-11 8:12 |SUCCESS| pw125894-125895 [PATCH] [2/2] " dpdklab
2023-04-11 8:16 dpdklab
2023-04-11 8:16 dpdklab
2023-04-11 8:17 dpdklab
2023-04-11 8:18 dpdklab
2023-04-11 8:20 dpdklab
2023-04-11 8:20 dpdklab
2023-04-11 8:27 dpdklab
2023-04-11 8:29 dpdklab
2023-04-11 8:31 dpdklab
2023-04-11 8:33 dpdklab
2023-04-11 8:34 dpdklab
2023-04-11 8:35 dpdklab
2023-04-11 8:36 dpdklab
2023-04-11 8:37 dpdklab
2023-04-11 8:43 dpdklab
2023-04-11 8:44 dpdklab
2023-04-11 8:47 dpdklab
2023-04-11 8:48 dpdklab
2023-04-11 8:49 dpdklab
2023-04-11 8:50 dpdklab
2023-04-11 8:56 dpdklab
2023-04-11 8:56 dpdklab
2023-04-11 9:00 dpdklab
2023-04-11 9:02 dpdklab
2023-04-11 9:03 dpdklab
2023-04-11 9:05 dpdklab
2023-04-11 9:09 dpdklab
2023-04-11 9:19 dpdklab
2023-04-11 9:21 dpdklab
2023-04-11 9:23 dpdklab
2023-04-11 9:33 dpdklab
2023-04-11 9:35 dpdklab
2023-04-11 9:38 dpdklab
2023-04-11 9:39 dpdklab
2023-04-11 9:40 dpdklab
2023-04-11 9:40 dpdklab
2023-04-11 9:44 dpdklab
2023-04-11 9:46 dpdklab
2023-04-11 9:49 dpdklab
2023-04-11 9:51 dpdklab
2023-04-11 9:55 dpdklab
2023-04-11 9:57 dpdklab
2023-04-11 10:01 dpdklab
2023-04-11 10:05 dpdklab
2023-04-11 10:06 dpdklab
2023-04-11 10:16 dpdklab
2023-04-11 10:24 dpdklab
2023-04-11 11:12 dpdklab
2023-04-11 11:16 dpdklab
2023-04-11 11:16 dpdklab
2023-04-11 15:26 dpdklab
2023-04-11 16:14 dpdklab
2023-04-12 21:27 dpdklab
2023-04-12 21:32 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=202304110652.33B6qBqm3093537@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).