From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139826 [PATCH v3] cmdline: increase input buffer size
Date: Fri, 3 May 2024 12:09:07 +0800 [thread overview]
Message-ID: <202405030409.443497TS685514@localhost.localdomain> (raw)
In-Reply-To: <20240503042715.344550-1-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139826
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Fri, 3 May 2024 07:27:14 +0300
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139826 --> 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-05-03 4:36 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240503042715.344550-1-getelson@nvidia.com>
2024-05-03 4:09 ` qemudev [this message]
2024-05-03 4:13 ` qemudev
2024-05-03 5:23 ` 0-day Robot
2024-05-03 5:40 ` |SUCCESS| pw139826 [PATCH] [v3] " dpdklab
2024-05-03 5:55 ` dpdklab
2024-05-03 6:03 ` dpdklab
2024-05-03 6:03 ` dpdklab
2024-05-03 6:04 ` dpdklab
2024-05-03 6:04 ` dpdklab
2024-05-03 6:10 ` dpdklab
2024-05-03 6:12 ` dpdklab
2024-05-03 6:18 ` dpdklab
2024-05-03 6:19 ` dpdklab
2024-05-03 6:19 ` dpdklab
2024-05-03 6:19 ` dpdklab
2024-05-03 6:19 ` dpdklab
2024-05-03 6:20 ` dpdklab
2024-05-03 6:20 ` dpdklab
2024-05-03 6:20 ` dpdklab
2024-05-03 6:21 ` dpdklab
2024-05-03 6:22 ` dpdklab
2024-05-03 6:22 ` dpdklab
2024-05-03 6:23 ` dpdklab
2024-05-03 6:24 ` dpdklab
2024-05-03 6:24 ` dpdklab
2024-05-03 6:31 ` dpdklab
2024-05-03 6:32 ` dpdklab
2024-05-03 6:33 ` dpdklab
2024-05-03 6:33 ` dpdklab
2024-05-03 6:33 ` dpdklab
2024-05-03 6:41 ` dpdklab
2024-05-03 6:43 ` dpdklab
2024-05-03 6:43 ` dpdklab
2024-05-03 6:43 ` dpdklab
2024-05-03 6:46 ` dpdklab
2024-05-03 6:47 ` dpdklab
2024-05-03 6:48 ` dpdklab
2024-05-03 6:48 ` dpdklab
2024-05-03 6:49 ` dpdklab
2024-05-03 6:50 ` dpdklab
2024-05-03 6:52 ` dpdklab
2024-05-03 6:53 ` dpdklab
2024-05-03 6:55 ` dpdklab
2024-05-03 6:55 ` dpdklab
2024-05-03 6:55 ` dpdklab
2024-05-03 6:59 ` dpdklab
2024-05-03 6:59 ` dpdklab
2024-05-03 7:00 ` dpdklab
2024-05-03 7:00 ` dpdklab
2024-05-03 7:01 ` dpdklab
2024-05-03 7:01 ` dpdklab
2024-05-03 7:02 ` dpdklab
2024-05-03 7:03 ` dpdklab
2024-05-03 7:03 ` dpdklab
2024-05-03 7:15 ` dpdklab
2024-05-03 7:15 ` dpdklab
2024-05-03 7:16 ` dpdklab
2024-05-03 7:17 ` dpdklab
2024-05-03 7:17 ` dpdklab
2024-05-03 7:17 ` dpdklab
2024-05-03 7:18 ` dpdklab
2024-05-03 7:18 ` dpdklab
2024-05-03 7:19 ` dpdklab
2024-05-03 7:25 ` dpdklab
2024-05-03 7:26 ` dpdklab
2024-05-03 7:45 ` dpdklab
2024-05-03 7:46 ` dpdklab
2024-05-03 7:48 ` dpdklab
2024-05-03 7:49 ` dpdklab
2024-05-03 7:50 ` dpdklab
2024-05-03 7:52 ` dpdklab
2024-05-03 7:54 ` dpdklab
2024-05-03 7:55 ` dpdklab
2024-05-03 7:56 ` dpdklab
2024-05-03 8:10 ` dpdklab
2024-05-03 8:11 ` dpdklab
2024-05-03 8:14 ` dpdklab
2024-05-03 8:19 ` |SUCCESS| pw139826 [PATCH v3] " checkpatch
2024-05-03 8:20 ` |SUCCESS| pw139826 [PATCH] [v3] " dpdklab
2024-05-03 8:34 ` dpdklab
2024-05-03 8:46 ` dpdklab
2024-05-03 8:55 ` dpdklab
2024-05-03 9:16 ` dpdklab
2024-05-03 9:33 ` dpdklab
2024-05-03 9:47 ` dpdklab
2024-05-03 9:48 ` |SUCCESS| pw139826 [PATCH v3] " checkpatch
2024-05-03 9:56 ` checkpatch
2024-05-03 17:54 ` |SUCCESS| pw139826 [PATCH] [v3] " dpdklab
2024-05-05 2:31 ` dpdklab
2024-05-05 2:35 ` dpdklab
2024-05-05 2:39 ` dpdklab
2024-05-05 2:43 ` dpdklab
2024-05-05 3:02 ` dpdklab
2024-05-06 10:23 ` 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=202405030409.443497TS685514@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).