From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147447-147451 [PATCH v2 13/13] net/ngbe: restrict configuration of VLAN strip offload
Date: Mon, 28 Oct 2024 09:39:38 +0800 [thread overview]
Message-ID: <202410280139.49S1dc0T2581070@localhost.localdomain> (raw)
In-Reply-To: <20241028023147.60157-14-jiawenwu@trustnetic.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/147451
_Compilation OK_
Submitter: Jiawen Wu <jiawenwu@trustnetic.com>
Date: Mon, 28 Oct 2024 10:31:35 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: b7f037995ce4f543136e135b9f14a035f31ddeed
147447-147451 --> 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:[~2024-10-28 2:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241028023147.60157-14-jiawenwu@trustnetic.com>
2024-10-28 1:39 ` qemudev [this message]
2024-10-28 1:44 ` qemudev
2024-10-28 2:10 ` |SUCCESS| pw147451 " checkpatch
2024-10-28 3:05 ` 0-day Robot
2024-10-28 3:15 ` |SUCCESS| pw147447-147451 [PATCH] [v2,13/13] net/ngbe: restrict conf dpdklab
2024-10-28 3:21 ` dpdklab
2024-10-28 3:25 ` dpdklab
2024-10-28 3:28 ` dpdklab
2024-10-28 3:31 ` dpdklab
2024-10-28 3:34 ` dpdklab
2024-10-28 3:35 ` dpdklab
2024-10-28 3:39 ` |PENDING| " dpdklab
2024-10-28 3:41 ` |SUCCESS| " dpdklab
2024-10-28 4:02 ` |PENDING| " dpdklab
2024-10-28 5:40 ` |WARNING| " dpdklab
2024-10-28 5:41 ` dpdklab
2024-10-28 5:44 ` dpdklab
2024-10-28 5:47 ` dpdklab
2024-10-28 5:48 ` dpdklab
2024-10-28 5:48 ` dpdklab
2024-10-28 5:55 ` 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=202410280139.49S1dc0T2581070@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).