From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw127112 [PATCH v4] ethdev: add indirect list flow action
Date: Fri, 19 May 2023 19:50:26 +0800 [thread overview]
Message-ID: <202305191150.34JBoQeG338006@localhost.localdomain> (raw)
In-Reply-To: <20230519115947.331304-1-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/127112
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Fri, 19 May 2023 14:59:47 +0300
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a399d7b5a994e335c446d4b15d7622d71dd8848c
127112 --> 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-19 12:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230519115947.331304-1-getelson@nvidia.com>
2023-05-19 11:50 ` qemudev [this message]
2023-05-19 11:54 ` qemudev
2023-05-19 12:01 ` |WARNING| " checkpatch
2023-05-19 12:59 ` |SUCCESS| " 0-day Robot
2023-05-19 13:08 |SUCCESS| pw127112 [PATCH] [v4] " dpdklab
2023-05-19 13:09 dpdklab
2023-05-19 13:13 dpdklab
2023-05-19 13:14 dpdklab
2023-05-19 13:14 dpdklab
2023-05-19 13:17 dpdklab
2023-05-19 13:22 dpdklab
2023-05-19 13:24 dpdklab
2023-05-19 13:29 dpdklab
2023-05-19 13:33 dpdklab
2023-05-19 13:36 dpdklab
2023-05-19 13:38 dpdklab
2023-05-19 13:48 dpdklab
2023-05-19 14:09 dpdklab
2023-05-19 14:10 dpdklab
2023-05-19 14:18 dpdklab
2023-05-19 14:18 dpdklab
2023-05-19 14:19 dpdklab
2023-05-19 14:19 dpdklab
2023-05-19 14:29 dpdklab
2023-05-19 14:33 dpdklab
2023-05-19 14:45 dpdklab
2023-05-19 14:52 dpdklab
2023-05-19 15:22 dpdklab
2023-05-19 20:55 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=202305191150.34JBoQeG338006@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).