From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138448 [PATCH] app/testpmd: fix auto completion for indirect list action
Date: Mon, 18 Mar 2024 18:29:25 +0800 [thread overview]
Message-ID: <202403181029.42IATPsZ2467659@localhost.localdomain> (raw)
In-Reply-To: <20240318092109.87656-1-shperetz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138448
_Compilation OK_
Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Mon, 18 Mar 2024 11:21:09 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 20db7deeb5131e46e859e212b334e8bef88ae701
138448 --> 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-18 10:54 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318092109.87656-1-shperetz@nvidia.com>
2024-03-18 10:29 ` qemudev [this message]
2024-03-18 10:33 ` qemudev
2024-03-18 10:51 ` checkpatch
2024-03-18 11:40 ` |SUCCESS| pw138448 [PATCH] app/testpmd: fix auto completion for indi dpdklab
2024-03-18 11:41 ` dpdklab
2024-03-18 11:41 ` dpdklab
2024-03-18 11:42 ` dpdklab
2024-03-18 11:42 ` dpdklab
2024-03-18 11:42 ` dpdklab
2024-03-18 11:43 ` dpdklab
2024-03-18 11:43 ` |SUCCESS| pw138448 [PATCH] app/testpmd: fix auto completion for indirect list action 0-day Robot
2024-03-18 11:43 ` |SUCCESS| pw138448 [PATCH] app/testpmd: fix auto completion for indi dpdklab
2024-03-18 11:44 ` dpdklab
2024-03-18 11:44 ` dpdklab
2024-03-18 11:44 ` dpdklab
2024-03-18 11:45 ` dpdklab
2024-03-18 11:45 ` dpdklab
2024-03-18 11:45 ` dpdklab
2024-03-18 11:46 ` dpdklab
2024-03-18 11:46 ` dpdklab
2024-03-18 11:46 ` dpdklab
2024-03-18 11:46 ` dpdklab
2024-03-18 11:46 ` dpdklab
2024-03-18 11:46 ` dpdklab
2024-03-18 11:47 ` dpdklab
2024-03-18 11:47 ` dpdklab
2024-03-18 11:47 ` dpdklab
2024-03-18 11:47 ` dpdklab
2024-03-18 11:48 ` dpdklab
2024-03-18 11:48 ` dpdklab
2024-03-18 11:48 ` dpdklab
2024-03-18 11:48 ` dpdklab
2024-03-18 11:48 ` dpdklab
2024-03-18 11:49 ` dpdklab
2024-03-18 11:49 ` dpdklab
2024-03-18 11:49 ` dpdklab
2024-03-18 11:49 ` dpdklab
2024-03-18 11:50 ` dpdklab
2024-03-18 11:50 ` dpdklab
2024-03-18 11:50 ` dpdklab
2024-03-18 11:50 ` dpdklab
2024-03-18 11:50 ` dpdklab
2024-03-18 11:51 ` dpdklab
2024-03-18 11:51 ` dpdklab
2024-03-18 11:51 ` dpdklab
2024-03-18 11:51 ` dpdklab
2024-03-18 11:51 ` dpdklab
2024-03-18 11:51 ` dpdklab
2024-03-18 11:52 ` dpdklab
2024-03-18 11:52 ` dpdklab
2024-03-18 11:52 ` dpdklab
2024-03-18 11:52 ` dpdklab
2024-03-18 11:52 ` dpdklab
2024-03-18 11:52 ` dpdklab
2024-03-18 11:55 ` dpdklab
2024-03-18 11:56 ` dpdklab
2024-03-18 11:56 ` dpdklab
2024-03-18 11:56 ` dpdklab
2024-03-18 11:56 ` dpdklab
2024-03-18 11:56 ` dpdklab
2024-03-18 11:57 ` dpdklab
2024-03-18 11:57 ` dpdklab
2024-03-18 11:58 ` dpdklab
2024-03-18 11:58 ` dpdklab
2024-03-18 11:59 ` dpdklab
2024-03-18 11:59 ` dpdklab
2024-03-18 11:59 ` dpdklab
2024-03-18 12:00 ` dpdklab
2024-03-18 12:18 ` dpdklab
2024-03-18 12:20 ` dpdklab
2024-03-18 12:25 ` dpdklab
2024-03-18 12:27 ` dpdklab
2024-03-18 12:32 ` dpdklab
2024-03-18 14:26 ` dpdklab
2024-03-20 13:19 ` dpdklab
2024-03-20 13:51 ` 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=202403181029.42IATPsZ2467659@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).