From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139018-139021 [PATCH 4/4] doc: replace use of ifconfig in nics
Date: Wed, 3 Apr 2024 00:10:55 +0800 [thread overview]
Message-ID: <202404021610.432GAtCP951619@localhost.localdomain> (raw)
In-Reply-To: <20240402163050.133923-5-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139021
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 2 Apr 2024 09:29:33 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139018-139021 --> 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-04-02 16:35 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240402163050.133923-5-stephen@networkplumber.org>
2024-04-02 16:10 ` qemudev [this message]
2024-04-02 16:15 ` qemudev
2024-04-02 16:33 ` |SUCCESS| pw139021 " checkpatch
2024-04-02 17:20 ` |SUCCESS| pw139018-139021 [PATCH] [4/4] doc: replace use of ifconfig dpdklab
2024-04-02 17:21 ` dpdklab
2024-04-02 17:21 ` dpdklab
2024-04-02 17:21 ` dpdklab
2024-04-02 17:21 ` dpdklab
2024-04-02 17:22 ` dpdklab
2024-04-02 17:22 ` dpdklab
2024-04-02 17:22 ` dpdklab
2024-04-02 17:22 ` dpdklab
2024-04-02 17:22 ` dpdklab
2024-04-02 17:23 ` dpdklab
2024-04-02 17:23 ` dpdklab
2024-04-02 17:23 ` dpdklab
2024-04-02 17:23 ` dpdklab
2024-04-02 17:23 ` dpdklab
2024-04-02 17:24 ` dpdklab
2024-04-02 17:25 ` dpdklab
2024-04-02 17:25 ` dpdklab
2024-04-02 17:25 ` |SUCCESS| pw139021 [PATCH 4/4] doc: replace use of ifconfig in nics 0-day Robot
2024-04-02 17:25 ` |SUCCESS| pw139018-139021 [PATCH] [4/4] doc: replace use of ifconfig dpdklab
2024-04-02 17:25 ` dpdklab
2024-04-02 17:26 ` dpdklab
2024-04-02 17:26 ` dpdklab
2024-04-02 17:27 ` dpdklab
2024-04-02 17:27 ` dpdklab
2024-04-02 17:27 ` dpdklab
2024-04-02 17:28 ` dpdklab
2024-04-02 17:28 ` dpdklab
2024-04-02 17:28 ` dpdklab
2024-04-02 17:28 ` dpdklab
2024-04-02 17:28 ` dpdklab
2024-04-02 17:29 ` dpdklab
2024-04-02 17:29 ` dpdklab
2024-04-02 17:29 ` dpdklab
2024-04-02 17:30 ` dpdklab
2024-04-02 17:30 ` dpdklab
2024-04-02 17:30 ` dpdklab
2024-04-02 17:30 ` dpdklab
2024-04-02 17:31 ` dpdklab
2024-04-02 17:31 ` dpdklab
2024-04-02 17:31 ` dpdklab
2024-04-02 17:32 ` dpdklab
2024-04-02 17:34 ` dpdklab
2024-04-02 17:35 ` dpdklab
2024-04-02 17:36 ` dpdklab
2024-04-02 17:36 ` dpdklab
2024-04-02 17:37 ` dpdklab
2024-04-02 17:37 ` dpdklab
2024-04-02 17:38 ` dpdklab
2024-04-02 17:39 ` dpdklab
2024-04-02 17:40 ` dpdklab
2024-04-02 17:40 ` dpdklab
2024-04-02 17:40 ` dpdklab
2024-04-02 17:40 ` dpdklab
2024-04-02 17:42 ` dpdklab
2024-04-02 17:42 ` dpdklab
2024-04-02 17:42 ` dpdklab
2024-04-02 17:44 ` dpdklab
2024-04-02 17:44 ` dpdklab
2024-04-02 17:45 ` dpdklab
2024-04-02 17:46 ` dpdklab
2024-04-02 17:48 ` dpdklab
2024-04-02 17:48 ` dpdklab
2024-04-02 17:50 ` dpdklab
2024-04-02 17:53 ` dpdklab
2024-04-02 17:54 ` dpdklab
2024-04-02 17:54 ` dpdklab
2024-04-02 17:55 ` dpdklab
2024-04-02 17:55 ` dpdklab
2024-04-02 17:57 ` dpdklab
2024-04-02 18:00 ` dpdklab
2024-04-02 18:01 ` dpdklab
2024-04-02 18:06 ` dpdklab
2024-04-02 18:06 ` dpdklab
2024-04-02 18:07 ` dpdklab
2024-04-02 18:07 ` dpdklab
2024-04-02 18:13 ` dpdklab
2024-04-02 18:15 ` dpdklab
2024-04-02 18:30 ` dpdklab
2024-04-02 20:01 ` dpdklab
2024-04-02 20:05 ` dpdklab
2024-04-03 18:41 ` dpdklab
2024-04-03 18:46 ` dpdklab
2024-04-03 18:56 ` dpdklab
2024-04-03 18:57 ` dpdklab
2024-04-03 19:42 ` 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=202404021610.432GAtCP951619@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).