From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126964 [PATCH v2] drivers/net/bnx2x : Add experimental 2.5Gbps support for BCM578xx.
Date: Thu, 18 May 2023 07:56:35 +0800 [thread overview]
Message-ID: <202305172356.34HNuZl42524470@localhost.localdomain> (raw)
In-Reply-To: <20230518000111.71360-1-julien_dpdk@jaube.fr>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126964
_Compilation OK_
Submitter: julien_dpdk@jaube.fr
Date: Thu, 18 May 2023 02:01:11 +0200
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: b6a5a2779cf9cdfc411509c4164ed2e6bd1b6444
126964 --> 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-05-18 0:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230518000111.71360-1-julien_dpdk@jaube.fr>
2023-05-17 23:56 ` qemudev [this message]
2023-05-18 0:00 ` qemudev
2023-05-18 0:02 ` |WARNING| " checkpatch
2023-05-18 1:00 ` |SUCCESS| " 0-day Robot
2023-05-18 0:53 |SUCCESS| pw126964 [PATCH] [v2] " dpdklab
2023-05-18 0:58 dpdklab
2023-05-18 0:59 dpdklab
2023-05-18 0:59 dpdklab
2023-05-18 0:59 dpdklab
2023-05-18 1:07 dpdklab
2023-05-18 1:07 dpdklab
2023-05-18 1:20 dpdklab
2023-05-18 1:28 dpdklab
2023-05-18 1:36 dpdklab
2023-05-18 1:40 dpdklab
2023-05-18 1:41 dpdklab
2023-05-18 1:45 dpdklab
2023-05-18 1:50 dpdklab
2023-05-18 1:54 dpdklab
2023-05-18 2:07 dpdklab
2023-05-18 2:10 dpdklab
2023-05-18 2:22 dpdklab
2023-05-18 2:29 dpdklab
2023-05-18 2:30 dpdklab
2023-05-18 2:35 dpdklab
2023-05-18 2:44 dpdklab
2023-05-18 2:47 dpdklab
2023-05-18 2:52 dpdklab
2023-05-18 2:53 dpdklab
2023-05-18 2:59 dpdklab
2023-05-18 3:40 dpdklab
2023-05-18 11:42 dpdklab
2023-05-18 11:42 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=202305172356.34HNuZl42524470@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).