From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148312 [PATCH] net/iavf: add segment-length check to Tx prep
Date: Tue, 12 Nov 2024 00:11:11 +0800 [thread overview]
Message-ID: <202411111611.4ABGBBvw1117796@localhost.localdomain> (raw)
In-Reply-To: <20241111164221.3031276-1-bruce.richardson@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148312
_Compilation OK_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Mon, 11 Nov 2024 16:42:20 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 7b121820e14bbd24197f83c9bbbe43883623b01e
148312 --> 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-11-11 16:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241111164221.3031276-1-bruce.richardson@intel.com>
2024-11-11 16:11 ` qemudev [this message]
2024-11-11 16:15 ` qemudev
2024-11-11 16:43 ` checkpatch
2024-11-11 18:45 ` 0-day Robot
2024-11-12 3:44 ` |SUCCESS| pw148312 [PATCH] net/iavf: add segment-length check to Tx dpdklab
2024-11-12 3:46 ` dpdklab
2024-11-12 3:47 ` dpdklab
2024-11-12 3:49 ` dpdklab
2024-11-12 3:56 ` dpdklab
2024-11-12 3:59 ` |PENDING| " dpdklab
2024-11-12 4:02 ` |SUCCESS| " dpdklab
2024-11-12 4:02 ` |PENDING| " dpdklab
2024-11-12 4:12 ` |SUCCESS| " dpdklab
2024-11-12 4:27 ` dpdklab
2024-11-12 4:31 ` dpdklab
2024-11-12 4:35 ` dpdklab
2024-11-12 4:36 ` |WARNING| " dpdklab
2024-11-12 4:39 ` |SUCCESS| " dpdklab
2024-11-12 4:50 ` dpdklab
2024-11-12 5:11 ` dpdklab
2024-11-12 6:46 ` 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=202411111611.4ABGBBvw1117796@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).