From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw127531 [PATCH] ethdev: fix indirect action convert
Date: Fri, 26 May 2023 11:07:08 +0800 [thread overview]
Message-ID: <202305260307.34Q378CK736775@localhost.localdomain> (raw)
In-Reply-To: <20230526031800.913744-1-suanmingm@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/127531
_Compilation OK_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Fri, 26 May 2023 06:18:00 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 7c7bfb93f11155cfcacde2372c3eaa5b0635b63f
127531 --> 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:[~2023-05-26 3:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230526031800.913744-1-suanmingm@nvidia.com>
2023-05-26 3:07 ` qemudev [this message]
2023-05-26 3:11 ` qemudev
2023-05-26 3:20 ` checkpatch
2023-05-26 4:39 ` 0-day Robot
2023-05-26 13:50 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-05-26 13:49 dpdklab
2023-05-26 12:16 dpdklab
2023-05-26 12:00 dpdklab
2023-05-26 11:51 dpdklab
2023-05-26 11:27 dpdklab
2023-05-26 11:13 dpdklab
2023-05-26 11:05 dpdklab
2023-05-26 7:54 dpdklab
2023-05-26 5:33 dpdklab
2023-05-26 5:18 dpdklab
2023-05-26 5:12 dpdklab
2023-05-26 5:07 dpdklab
2023-05-26 5:07 dpdklab
2023-05-26 5:07 dpdklab
2023-05-26 5:06 dpdklab
2023-05-26 5:03 dpdklab
2023-05-26 5:02 dpdklab
2023-05-26 4:52 dpdklab
2023-05-26 4:51 dpdklab
2023-05-26 4:49 dpdklab
2023-05-26 4:38 dpdklab
2023-05-26 4:19 dpdklab
2023-05-26 4:17 dpdklab
2023-05-26 4:03 dpdklab
2023-05-26 4:03 dpdklab
2023-05-26 4:03 dpdklab
2023-05-26 3:58 dpdklab
2023-05-26 3:52 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=202305260307.34Q378CK736775@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).