From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125802-125811 [PATCH v2 10/10] net/octeon_ep: set secondary process dev ops
Date: Wed, 5 Apr 2023 22:17:29 +0800 [thread overview]
Message-ID: <202304051417.335EHTnr3758137@localhost.localdomain> (raw)
In-Reply-To: <20230405142537.1899973-11-sedara@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125811
_Compilation OK_
Submitter: Sathesh Edara <sedara@marvell.com>
Date: Wed, 5 Apr 2023 07:25:27 -0700
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: a0631bcf54745b927d2824078e0a0b7ac0f48748
125802-125811 --> 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-05 14:31 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230405142537.1899973-11-sedara@marvell.com>
2023-04-05 14:17 ` qemudev [this message]
2023-04-05 14:21 ` qemudev
2023-04-05 14:28 ` |SUCCESS| pw125811 " checkpatch
2023-04-05 15:18 ` 0-day Robot
2023-04-05 22:12 |SUCCESS| pw125802-125811 [PATCH] [v2, " dpdklab
2023-04-05 22:12 dpdklab
2023-04-05 22:14 dpdklab
2023-04-05 22:17 dpdklab
2023-04-05 22:19 dpdklab
2023-04-05 22:21 dpdklab
2023-04-05 22:27 dpdklab
2023-04-05 22:28 dpdklab
2023-04-05 22:32 dpdklab
2023-04-05 22:33 dpdklab
2023-04-05 22:44 dpdklab
2023-04-05 22:46 dpdklab
2023-04-05 22:47 dpdklab
2023-04-05 22:50 dpdklab
2023-04-05 22:56 dpdklab
2023-04-05 23:57 dpdklab
2023-04-05 23:58 dpdklab
2023-04-06 0:00 dpdklab
2023-04-06 0:01 dpdklab
2023-04-06 0:04 dpdklab
2023-04-06 0:05 dpdklab
2023-04-06 0:06 dpdklab
2023-04-06 0:10 dpdklab
2023-04-06 0:10 dpdklab
2023-04-06 0:12 dpdklab
2023-04-06 0:13 dpdklab
2023-04-06 0:17 dpdklab
2023-04-06 0:17 dpdklab
2023-04-06 0:21 dpdklab
2023-04-06 0:26 dpdklab
2023-04-06 0:30 dpdklab
2023-04-06 0:30 dpdklab
2023-04-06 9:45 dpdklab
2023-04-06 9:46 dpdklab
2023-04-06 9:59 dpdklab
2023-04-06 10:01 dpdklab
2023-04-06 10:03 dpdklab
2023-04-06 10:03 dpdklab
2023-04-06 10:09 dpdklab
2023-04-06 10:14 dpdklab
2023-04-06 10:36 dpdklab
2023-04-06 10:38 dpdklab
2023-04-06 10:44 dpdklab
2023-04-06 10:44 dpdklab
2023-04-06 11:06 dpdklab
2023-04-06 11:35 dpdklab
2023-04-06 12:06 dpdklab
2023-04-06 12:08 dpdklab
2023-04-06 12:08 dpdklab
2023-04-06 12:41 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=202304051417.335EHTnr3758137@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).