From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138136 [RFC v2] eal: increase passed max multi-process file descriptors
Date: Sat, 9 Mar 2024 04:14:15 +0800 [thread overview]
Message-ID: <202403082014.428KEFHa1564753@localhost.localdomain> (raw)
In-Reply-To: <20240308203737.208999-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138136
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 8 Mar 2024 12:36:39 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a86f381b826660e88794754c41d3aec79ce9b87c
138136 --> 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-03-08 20:39 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240308203737.208999-1-stephen@networkplumber.org>
2024-03-08 20:14 ` qemudev [this message]
2024-03-08 20:18 ` qemudev
2024-03-08 20:39 ` checkpatch
2024-03-08 21:23 ` |FAILURE| " 0-day Robot
2024-03-08 21:52 ` |SUCCESS| pw138136 [PATCH] [RFC,v2] eal: increase passed max multi-p dpdklab
2024-03-08 21:56 ` dpdklab
2024-03-08 21:57 ` dpdklab
2024-03-08 22:03 ` dpdklab
2024-03-08 22:03 ` dpdklab
2024-03-08 22:04 ` |WARNING| " dpdklab
2024-03-08 22:04 ` |SUCCESS| " dpdklab
2024-03-08 22:05 ` dpdklab
2024-03-08 22:05 ` |WARNING| " dpdklab
2024-03-08 22:06 ` dpdklab
2024-03-08 22:06 ` |SUCCESS| " dpdklab
2024-03-08 22:06 ` |WARNING| " dpdklab
2024-03-08 22:06 ` |SUCCESS| " dpdklab
2024-03-08 22:07 ` |WARNING| " dpdklab
2024-03-08 22:08 ` |SUCCESS| " dpdklab
2024-03-08 22:08 ` dpdklab
2024-03-08 22:08 ` dpdklab
2024-03-08 22:09 ` |WARNING| " dpdklab
2024-03-08 22:09 ` |SUCCESS| " dpdklab
2024-03-08 22:10 ` |WARNING| " dpdklab
2024-03-08 22:10 ` |SUCCESS| " dpdklab
2024-03-08 22:15 ` |WARNING| " dpdklab
2024-03-08 22:16 ` |SUCCESS| " dpdklab
2024-03-08 22:16 ` dpdklab
2024-03-08 22:18 ` dpdklab
2024-03-08 22:19 ` dpdklab
2024-03-08 22:19 ` dpdklab
2024-03-08 22:19 ` dpdklab
2024-03-08 22:19 ` |WARNING| " dpdklab
2024-03-08 22:20 ` dpdklab
2024-03-08 22:21 ` |SUCCESS| " dpdklab
2024-03-08 22:24 ` dpdklab
2024-03-08 22:24 ` dpdklab
2024-03-08 22:25 ` dpdklab
2024-03-08 22:25 ` dpdklab
2024-03-08 22:25 ` dpdklab
2024-03-08 22:25 ` dpdklab
2024-03-08 22:26 ` dpdklab
2024-03-08 22:26 ` dpdklab
2024-03-08 22:26 ` dpdklab
2024-03-08 22:26 ` dpdklab
2024-03-08 22:27 ` dpdklab
2024-03-08 22:29 ` dpdklab
2024-03-08 22:30 ` dpdklab
2024-03-08 22:30 ` dpdklab
2024-03-08 22:30 ` dpdklab
2024-03-08 22:31 ` dpdklab
2024-03-08 22:31 ` dpdklab
2024-03-08 22:32 ` dpdklab
2024-03-08 22:32 ` dpdklab
2024-03-08 22:42 ` dpdklab
2024-03-08 22:45 ` dpdklab
2024-03-08 22:54 ` dpdklab
2024-03-08 22:54 ` dpdklab
2024-03-08 22:56 ` dpdklab
2024-03-08 22:56 ` dpdklab
2024-03-08 22:57 ` dpdklab
2024-03-08 22:59 ` dpdklab
2024-03-08 22:59 ` dpdklab
2024-03-08 22:59 ` dpdklab
2024-03-08 23:04 ` dpdklab
2024-03-08 23:27 ` dpdklab
2024-03-08 23:38 ` dpdklab
2024-03-08 23:41 ` dpdklab
2024-03-08 23:56 ` dpdklab
2024-03-08 23:57 ` dpdklab
2024-03-09 0:00 ` dpdklab
2024-03-09 0:55 ` dpdklab
2024-03-09 1:12 ` dpdklab
2024-03-09 1:18 ` dpdklab
2024-03-09 1:30 ` dpdklab
2024-03-13 12:57 ` dpdklab
2024-03-13 13:38 ` 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=202403082014.428KEFHa1564753@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).