From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw149123 [PATCH v2] MAINTAINERS: change maintainer for next-net
Date: Wed, 11 Dec 2024 04:16:25 +0800 [thread overview]
Message-ID: <202412102016.4BAKGPn82385095@localhost.localdomain> (raw)
In-Reply-To: <20241210204156.15393-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/149123
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 10 Dec 2024 12:41:55 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7df61db6c387703a36306c1aea92225921e2eeb2
149123 --> 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-12-10 20:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241210204156.15393-1-stephen@networkplumber.org>
2024-12-10 20:16 ` qemudev [this message]
2024-12-10 20:20 ` qemudev
2024-12-10 20:43 ` checkpatch
2024-12-10 21:18 ` |PENDING| pw149123 [PATCH] [v2] MAINTAINERS: change maintainer for n dpdklab
2024-12-10 21:25 ` |SUCCESS| " dpdklab
2024-12-10 21:27 ` |PENDING| " dpdklab
2024-12-10 21:39 ` |SUCCESS| " dpdklab
2024-12-10 21:41 ` dpdklab
2024-12-10 21:42 ` dpdklab
2024-12-10 21:44 ` dpdklab
2024-12-10 21:49 ` dpdklab
2024-12-10 21:50 ` dpdklab
2024-12-10 21:55 ` dpdklab
2024-12-10 21:59 ` dpdklab
2024-12-10 22:03 ` dpdklab
2024-12-10 22:09 ` |WARNING| " dpdklab
2024-12-10 22:10 ` |SUCCESS| " dpdklab
2024-12-11 0:32 ` dpdklab
2024-12-11 1:02 ` |SUCCESS| pw149123 [PATCH v2] MAINTAINERS: change maintainer for next-net 0-day Robot
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=202412102016.4BAKGPn82385095@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).