From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw146046 [PATCH] net/nfp: fix RSS failed on VXLAN inner layer
Date: Wed, 16 Oct 2024 16:32:38 +0800 [thread overview]
Message-ID: <202410160832.49G8WchH881367@localhost.localdomain> (raw)
In-Reply-To: <20241016081759.4005301-1-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/146046
_Compilation OK_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Wed, 16 Oct 2024 16:17:59 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: f2e424aeb6edf8c4990abf266aaa8814a8050616
146046 --> 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:[~2024-10-16 9:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241016081759.4005301-1-chaoyong.he@corigine.com>
2024-10-16 8:18 ` checkpatch
2024-10-16 8:32 ` qemudev [this message]
2024-10-16 8:37 ` qemudev
2024-10-16 9:22 ` 0-day Robot
2024-10-16 10:02 ` |SUCCESS| pw146046 [PATCH] net/nfp: fix RSS failed on VXLAN inner la dpdklab
2024-10-16 10:06 ` dpdklab
2024-10-16 10:11 ` dpdklab
2024-10-16 10:15 ` dpdklab
2024-10-16 10:19 ` dpdklab
2024-10-16 11:39 ` dpdklab
2024-10-16 11:45 ` dpdklab
2024-10-16 14:01 ` dpdklab
2024-10-16 14:09 ` dpdklab
2024-10-16 14:34 ` dpdklab
2024-10-16 22:25 ` |PENDING| " dpdklab
2024-10-16 22:54 ` dpdklab
2024-10-16 23:20 ` dpdklab
2024-10-17 0:59 ` dpdklab
2024-10-17 1:05 ` |FAILURE| " dpdklab
2024-10-17 1:06 ` dpdklab
2024-10-17 1:06 ` dpdklab
2024-10-17 1:12 ` |SUCCESS| " dpdklab
2024-10-17 1:13 ` dpdklab
2024-10-17 2:06 ` |FAILURE| " dpdklab
2024-10-17 4:33 ` |SUCCESS| " dpdklab
2024-10-17 5:58 ` dpdklab
2024-10-17 8:08 ` dpdklab
2024-10-19 11:31 ` 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=202410160832.49G8WchH881367@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).