From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124297-124299 [PATCH v1 2/2] net/octeon_ep: support port kind
Date: Tue, 21 Feb 2023 22:27:03 +0800 [thread overview]
Message-ID: <202302211427.31LER3je987525@localhost.localdomain> (raw)
In-Reply-To: <20230221143627.219917-3-sedara@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124299
_Compilation OK_
Submitter: Sathesh Edara <sedara@marvell.com>
Date: Tue, 21 Feb 2023 06:36:25 -0800
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: b44d40a2e75cfa4d8708693fdff32643903f12d3
124297-124299 --> 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-02-21 14:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230221143627.219917-3-sedara@marvell.com>
2023-02-21 14:27 ` qemudev [this message]
2023-02-21 14:31 ` qemudev
2023-02-21 14:37 ` |SUCCESS| pw124299 " checkpatch
2023-02-21 17:39 ` 0-day Robot
2023-02-23 11:14 |SUCCESS| pw124297-124299 [PATCH] [v1, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-21 21:04 dpdklab
2023-02-21 21:04 dpdklab
2023-02-21 20:57 dpdklab
2023-02-21 20:53 dpdklab
2023-02-21 20:53 dpdklab
2023-02-21 20:46 dpdklab
2023-02-21 20:45 dpdklab
2023-02-21 20:43 dpdklab
2023-02-21 20:43 dpdklab
2023-02-21 20:39 dpdklab
2023-02-21 20:25 dpdklab
2023-02-21 20:20 dpdklab
2023-02-21 20:20 dpdklab
2023-02-21 20:16 dpdklab
2023-02-21 20:08 dpdklab
2023-02-21 18:34 dpdklab
2023-02-21 18:26 dpdklab
2023-02-21 18:17 dpdklab
2023-02-21 18:01 dpdklab
2023-02-21 18:00 dpdklab
2023-02-21 17:57 dpdklab
2023-02-21 17:51 dpdklab
2023-02-21 17:47 dpdklab
2023-02-21 17:36 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=202302211427.31LER3je987525@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).