From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125227 [PATCH] doc: deprecation notice to remove net/bnx2x driver
Date: Fri, 17 Mar 2023 20:20:12 +0800 [thread overview]
Message-ID: <202303171220.32HCKCkt1271512@localhost.localdomain> (raw)
In-Reply-To: <20230317123011.3146170-1-jerinj@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125227
_Compilation OK_
Submitter: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Date: Fri, 17 Mar 2023 18:00:11 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: ce5440e0350df101443aa4d0e96bea0a06ef9364
125227 --> 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-03-17 12:34 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230317123011.3146170-1-jerinj@marvell.com>
2023-03-17 12:20 ` qemudev [this message]
2023-03-17 12:24 ` qemudev
2023-03-17 12:31 ` checkpatch
2023-03-17 14:59 ` |SUCCESS| pw125227 [dpdk-dev] " 0-day Robot
2023-03-17 13:06 |SUCCESS| pw125227 " dpdklab
2023-03-17 13:12 dpdklab
2023-03-17 13:18 dpdklab
2023-03-17 13:19 dpdklab
2023-03-17 13:20 dpdklab
2023-03-17 13:22 dpdklab
2023-03-17 13:28 dpdklab
2023-03-17 13:28 dpdklab
2023-03-17 13:33 dpdklab
2023-03-17 13:33 dpdklab
2023-03-17 13:34 dpdklab
2023-03-17 13:34 dpdklab
2023-03-17 13:37 dpdklab
2023-03-17 13:44 dpdklab
2023-03-17 13:45 dpdklab
2023-03-17 13:48 dpdklab
2023-03-17 13:53 dpdklab
2023-03-17 13:54 dpdklab
2023-03-17 13:57 dpdklab
2023-03-17 13:58 dpdklab
2023-03-17 14:02 dpdklab
2023-03-17 14:09 dpdklab
2023-03-17 14:10 dpdklab
2023-03-17 14:59 dpdklab
2023-03-17 15:02 dpdklab
2023-03-17 15:05 dpdklab
2023-03-19 10:51 dpdklab
2023-03-19 10:52 dpdklab
2023-03-19 19:26 dpdklab
2023-03-19 20:14 dpdklab
2023-03-20 8:24 dpdklab
2023-03-20 9:38 dpdklab
2023-03-20 9:46 dpdklab
2023-03-20 9:50 dpdklab
2023-03-20 9:52 dpdklab
2023-03-20 10:01 dpdklab
2023-03-20 10:03 dpdklab
2023-03-20 10:04 dpdklab
2023-03-20 10:12 dpdklab
2023-03-20 10:20 dpdklab
2023-03-20 10:24 dpdklab
2023-03-20 10:24 dpdklab
2023-03-20 10:24 dpdklab
2023-03-20 10:47 dpdklab
2023-03-20 12:32 dpdklab
2023-03-20 12:34 dpdklab
2023-03-20 12:39 dpdklab
2023-03-20 12:44 dpdklab
2023-03-20 12:48 dpdklab
2023-03-20 12:50 dpdklab
2023-03-20 12:56 dpdklab
2023-03-20 13:03 dpdklab
2023-03-20 13:04 dpdklab
2023-03-20 13:09 dpdklab
2023-03-20 13:13 dpdklab
2023-03-20 13:17 dpdklab
2023-03-20 13:17 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=202303171220.32HCKCkt1271512@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).