From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124889 [PATCH] doc: deprecation notice to remove LiquidIO ethdev driver
Date: Thu, 9 Mar 2023 14:56:36 +0800 [thread overview]
Message-ID: <202303090656.3296uar81855682@localhost.localdomain> (raw)
In-Reply-To: <20230309070733.537242-1-jerinj@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124889
_Compilation OK_
Submitter: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Date: Thu, 9 Mar 2023 12:37:33 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 8a44b2a511114d9bc658d934d6cf16a3d8150d6d
124889 --> 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-09 7:10 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230309070733.537242-1-jerinj@marvell.com>
2023-03-09 6:56 ` qemudev [this message]
2023-03-09 7:00 ` qemudev
2023-03-09 7:09 ` |WARNING| " checkpatch
2023-03-09 9:39 ` |SUCCESS| pw124889 [dpdk-dev] " 0-day Robot
2023-03-11 2:06 |SUCCESS| pw124889 " dpdklab
2023-03-11 2:08 dpdklab
2023-03-11 2:12 dpdklab
2023-03-11 2:12 dpdklab
2023-03-11 2:17 dpdklab
2023-03-11 2:18 dpdklab
2023-03-11 2:23 dpdklab
2023-03-11 2:23 dpdklab
2023-03-11 2:24 dpdklab
2023-03-11 2:25 dpdklab
2023-03-11 2:28 dpdklab
2023-03-11 2:29 dpdklab
2023-03-11 2:32 dpdklab
2023-03-11 2:34 dpdklab
2023-03-11 2:37 dpdklab
2023-03-11 2:37 dpdklab
2023-03-11 2:40 dpdklab
2023-03-11 2:43 dpdklab
2023-03-11 2:45 dpdklab
2023-03-11 2:47 dpdklab
2023-03-11 2:50 dpdklab
2023-03-11 2:50 dpdklab
2023-03-11 2:50 dpdklab
2023-03-11 2:53 dpdklab
2023-03-11 2:59 dpdklab
2023-03-11 3:02 dpdklab
2023-03-11 3:03 dpdklab
2023-03-11 3:11 dpdklab
2023-03-11 19:53 dpdklab
2023-03-11 21:03 dpdklab
2023-03-11 21:20 dpdklab
2023-03-11 21:23 dpdklab
2023-03-12 8:42 dpdklab
2023-03-12 8:54 dpdklab
2023-03-12 8:57 dpdklab
2023-03-12 8:59 dpdklab
2023-03-12 9:01 dpdklab
2023-03-12 9:01 dpdklab
2023-03-12 9:04 dpdklab
2023-03-12 9:07 dpdklab
2023-03-12 9:07 dpdklab
2023-03-12 9:08 dpdklab
2023-03-12 9:09 dpdklab
2023-03-12 9:12 dpdklab
2023-03-12 9:23 dpdklab
2023-03-12 9:30 dpdklab
2023-03-12 9:32 dpdklab
2023-03-12 9:45 dpdklab
2023-03-12 9:45 dpdklab
2023-03-12 9:47 dpdklab
2023-03-12 9:47 dpdklab
2023-03-12 9:55 dpdklab
2023-03-12 10:01 dpdklab
2023-03-12 10:02 dpdklab
2023-03-12 10:10 dpdklab
2023-03-12 10:24 dpdklab
2023-03-12 10:32 dpdklab
2023-03-12 10:39 dpdklab
2023-03-12 10:41 dpdklab
2023-03-12 10:41 dpdklab
2023-03-12 20:01 dpdklab
2023-03-12 21:44 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=202303090656.3296uar81855682@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).