From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw128451 [PATCH] net/nfp: fix TP flow action for UDP
Date: Fri, 9 Jun 2023 14:12:04 +0800 [thread overview]
Message-ID: <202306090612.3596C4xf2807197@localhost.localdomain> (raw)
In-Reply-To: <20230609062219.1308140-1-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/128451
_Compilation OK_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Fri, 9 Jun 2023 14:22:19 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: e5cb7ea1f4c45fa147442a248dce0fdffd907291
128451 --> 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-06-09 6:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230609062219.1308140-1-chaoyong.he@corigine.com>
2023-06-09 6:12 ` qemudev [this message]
2023-06-09 6:16 ` qemudev
2023-06-09 6:24 ` checkpatch
2023-06-09 7:39 ` 0-day Robot
2023-06-09 7:27 dpdklab
2023-06-09 7:27 dpdklab
2023-06-09 7:28 dpdklab
2023-06-09 7:28 dpdklab
2023-06-09 7:28 dpdklab
2023-06-09 7:28 dpdklab
2023-06-09 7:34 dpdklab
2023-06-09 7:38 dpdklab
2023-06-09 7:41 dpdklab
2023-06-09 7:45 dpdklab
2023-06-09 7:46 dpdklab
2023-06-09 7:46 dpdklab
2023-06-09 7:46 dpdklab
2023-06-09 7:49 dpdklab
2023-06-09 7:49 dpdklab
2023-06-09 7:56 dpdklab
2023-06-09 8:12 dpdklab
2023-06-09 8:15 dpdklab
2023-06-09 8:16 dpdklab
2023-06-09 8:16 dpdklab
2023-06-09 8:24 dpdklab
2023-06-09 8:24 dpdklab
2023-06-09 11:08 dpdklab
2023-06-09 11:09 dpdklab
2023-06-09 16:41 dpdklab
2023-06-09 16:46 dpdklab
2023-06-09 17:02 dpdklab
2023-06-09 17:06 dpdklab
2023-06-09 17:16 dpdklab
2023-06-10 15:28 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=202306090612.3596C4xf2807197@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).