From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140540 [PATCH v2] dumpcap: add lcores option
Date: Sat, 1 Jun 2024 07:08:25 +0800 [thread overview]
Message-ID: <202405312308.44VN8Pbg1599722@localhost.localdomain> (raw)
In-Reply-To: <20240531233450.6979-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140540
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 31 May 2024 16:33:55 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 76cef1af8bdaeaf67a5c4ca5df3f221df994dc46
140540 --> 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-31 23:37 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240531233450.6979-1-stephen@networkplumber.org>
2024-05-31 23:08 ` qemudev [this message]
2024-05-31 23:12 ` qemudev
2024-05-31 23:35 ` checkpatch
2024-06-01 0:23 ` 0-day Robot
2024-06-01 16:36 ` |SUCCESS| pw140540 [PATCH] [v2] " dpdklab
2024-06-01 16:37 ` dpdklab
2024-06-01 16:38 ` dpdklab
2024-06-01 16:38 ` dpdklab
2024-06-01 16:42 ` dpdklab
2024-06-01 16:42 ` dpdklab
2024-06-01 16:43 ` dpdklab
2024-06-01 16:54 ` dpdklab
2024-06-01 16:54 ` dpdklab
2024-06-01 16:56 ` dpdklab
2024-06-01 16:57 ` dpdklab
2024-06-01 16:57 ` dpdklab
2024-06-01 16:57 ` dpdklab
2024-06-01 16:59 ` dpdklab
2024-06-01 17:01 ` dpdklab
2024-06-01 17:01 ` dpdklab
2024-06-01 17:26 ` dpdklab
2024-06-01 18:20 ` dpdklab
2024-06-01 18:23 ` dpdklab
2024-06-01 18:27 ` dpdklab
2024-06-01 18:33 ` dpdklab
2024-06-01 18:34 ` dpdklab
2024-06-01 18:34 ` dpdklab
2024-06-01 18:40 ` dpdklab
2024-06-01 18:51 ` dpdklab
2024-06-01 18:52 ` dpdklab
2024-06-01 18:53 ` dpdklab
2024-06-01 18:58 ` dpdklab
2024-06-01 19:00 ` dpdklab
2024-06-01 19:01 ` dpdklab
2024-06-01 19:15 ` dpdklab
2024-06-01 19:17 ` dpdklab
2024-06-01 19:17 ` dpdklab
2024-06-01 19:18 ` dpdklab
2024-06-01 19:23 ` dpdklab
2024-06-01 19:27 ` dpdklab
2024-06-01 19:36 ` dpdklab
2024-06-01 19:40 ` dpdklab
2024-06-01 19:40 ` dpdklab
2024-06-01 19:44 ` dpdklab
2024-06-01 19:45 ` dpdklab
2024-06-01 19:46 ` dpdklab
2024-06-01 19:47 ` dpdklab
2024-06-01 19:48 ` dpdklab
2024-06-01 19:48 ` dpdklab
2024-06-01 19:50 ` dpdklab
2024-06-01 19:52 ` dpdklab
2024-06-01 19:52 ` dpdklab
2024-06-01 19:53 ` dpdklab
2024-06-01 19:53 ` dpdklab
2024-06-01 19:55 ` dpdklab
2024-06-01 19:57 ` dpdklab
2024-06-01 19:59 ` dpdklab
2024-06-01 20:02 ` dpdklab
2024-06-01 20:05 ` dpdklab
2024-06-01 20:06 ` dpdklab
2024-06-01 20:24 ` dpdklab
2024-06-01 20:25 ` dpdklab
2024-06-01 20:29 ` dpdklab
2024-06-01 20:32 ` dpdklab
2024-06-01 20:34 ` dpdklab
2024-06-01 20:35 ` dpdklab
2024-06-01 20:37 ` dpdklab
2024-06-01 20:39 ` dpdklab
2024-06-01 20:43 ` dpdklab
2024-06-01 20:47 ` dpdklab
2024-06-01 20:49 ` dpdklab
2024-06-01 20:49 ` dpdklab
2024-06-01 20:52 ` dpdklab
2024-06-01 20:53 ` dpdklab
2024-06-01 20:55 ` dpdklab
2024-06-01 20:57 ` dpdklab
2024-06-01 20:58 ` dpdklab
2024-06-01 20:59 ` dpdklab
2024-06-01 21:00 ` dpdklab
2024-06-01 21:00 ` dpdklab
2024-06-01 21:02 ` dpdklab
2024-06-01 21:02 ` dpdklab
2024-06-01 21:02 ` dpdklab
2024-06-01 21:04 ` dpdklab
2024-06-01 21:06 ` dpdklab
2024-06-01 21:16 ` dpdklab
2024-06-01 21:24 ` dpdklab
2024-06-01 21:55 ` dpdklab
2024-06-01 21:59 ` dpdklab
2024-06-01 22:03 ` dpdklab
2024-06-01 22:23 ` dpdklab
2024-06-01 22:26 ` dpdklab
2024-06-01 23:16 ` dpdklab
2024-06-01 23:18 ` dpdklab
2024-06-01 23:45 ` dpdklab
2024-06-01 23:58 ` dpdklab
2024-06-02 6:09 ` 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=202405312308.44VN8Pbg1599722@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).