From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw154862 [PATCH] net/r8169: add missing newline at end of meson.build
Date: Mon, 30 Jun 2025 23:37:20 +0800 [thread overview]
Message-ID: <202506301537.55UFbKTw336157@localhost.localdomain> (raw)
In-Reply-To: <20250630160533.126163-2-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/154862
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 30 Jun 2025 09:05:34 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 83fd93a45061029c8a7850e15114e5932e7d045c
154862 --> 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:[~2025-06-30 16:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250630160533.126163-2-stephen@networkplumber.org>
2025-06-30 15:37 ` qemudev [this message]
2025-06-30 15:42 ` qemudev
2025-06-30 16:05 ` checkpatch
2025-06-30 17:22 ` 0-day Robot
2025-06-30 17:31 ` |PENDING| pw154862 [PATCH] net/r8169: add missing newline at end of dpdklab
2025-06-30 17:37 ` |SUCCESS| " dpdklab
2025-06-30 17:37 ` dpdklab
2025-06-30 17:55 ` dpdklab
2025-06-30 18:05 ` dpdklab
2025-06-30 18:09 ` |PENDING| " dpdklab
2025-06-30 19:09 ` |SUCCESS| " dpdklab
2025-06-30 19:33 ` dpdklab
2025-06-30 19:40 ` dpdklab
2025-06-30 20:05 ` |PENDING| " dpdklab
2025-06-30 20:13 ` |FAILURE| " dpdklab
2025-06-30 20:38 ` dpdklab
2025-06-30 21:20 ` |PENDING| " dpdklab
2025-06-30 21:40 ` |SUCCESS| " dpdklab
2025-06-30 21:40 ` dpdklab
2025-06-30 21:41 ` dpdklab
2025-06-30 21:41 ` dpdklab
2025-06-30 21:42 ` dpdklab
2025-06-30 22:02 ` |WARNING| " dpdklab
2025-07-01 1:35 ` |SUCCESS| " dpdklab
2025-07-01 2:02 ` dpdklab
2025-07-01 3:12 ` 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=202506301537.55UFbKTw336157@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).