From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124566 [PATCH] net/nfp: fix the offload of multiple output actions
Date: Wed, 1 Mar 2023 16:18:38 +0800 [thread overview]
Message-ID: <202303010818.3218IcqL952805@localhost.localdomain> (raw)
In-Reply-To: <20230228090305.501732-1-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124566
_Compilation OK_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Tue, 28 Feb 2023 17:03:05 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: f09877166b29c89e8a602e0fd5b1289b26a88e8c
124566 --> 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 prev parent reply other threads:[~2023-03-01 8:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230228090305.501732-1-chaoyong.he@corigine.com>
2023-02-28 9:04 ` checkpatch
2023-02-28 10:59 ` 0-day Robot
2023-03-01 8:18 ` qemudev [this message]
2023-03-01 8:19 ` qemudev
2023-02-28 9:35 dpdklab
2023-02-28 9:40 dpdklab
2023-02-28 9:41 dpdklab
2023-02-28 9:46 dpdklab
2023-02-28 9:52 dpdklab
2023-02-28 9:54 dpdklab
2023-02-28 10:07 dpdklab
2023-02-28 10:39 dpdklab
2023-02-28 10:58 dpdklab
2023-02-28 11:00 dpdklab
2023-02-28 11:11 dpdklab
2023-02-28 11:14 dpdklab
2023-02-28 11:16 dpdklab
2023-02-28 11:22 dpdklab
2023-02-28 11:24 dpdklab
2023-02-28 11:24 dpdklab
2023-02-28 11:25 dpdklab
2023-02-28 11:29 dpdklab
2023-02-28 11:33 dpdklab
2023-02-28 11:35 dpdklab
2023-02-28 11:37 dpdklab
2023-02-28 11:53 dpdklab
2023-02-28 11:57 dpdklab
2023-02-28 11:57 dpdklab
2023-02-28 12:05 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=202303010818.3218IcqL952805@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).