From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123516 [PATCH v6] ethdev: add flow rule group description
Date: Thu, 9 Feb 2023 15:22:00 +0800 [thread overview]
Message-ID: <202302090722.3197M0Ir4074436@localhost.localdomain> (raw)
In-Reply-To: <20230209073237.3185852-1-rongweil@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123516
_Compilation OK_
Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Thu, 9 Feb 2023 09:32:37 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 2ca47d99046e0e60c03e5d5b0bade68915a960cf
123516 --> 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-02-09 7:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230209073237.3185852-1-rongweil@nvidia.com>
2023-02-09 7:22 ` qemudev [this message]
2023-02-09 7:25 ` qemudev
2023-02-09 7:34 ` checkpatch
2023-02-09 8:19 ` 0-day Robot
2023-02-09 8:03 |SUCCESS| pw123516 [PATCH] [v6] " dpdklab
2023-02-09 8:08 dpdklab
2023-02-09 8:08 dpdklab
2023-02-09 8:11 dpdklab
2023-02-09 8:12 dpdklab
2023-02-09 8:14 dpdklab
2023-02-09 8:15 dpdklab
2023-02-09 8:18 dpdklab
2023-02-09 8:19 dpdklab
2023-02-09 8:23 dpdklab
2023-02-09 8:26 dpdklab
2023-02-09 8:31 dpdklab
2023-02-09 8:39 dpdklab
2023-02-09 9:33 dpdklab
2023-02-10 13:31 dpdklab
2023-02-10 13:44 dpdklab
2023-02-10 14:04 dpdklab
2023-02-10 14:05 dpdklab
2023-02-10 14:07 dpdklab
2023-02-10 14:08 dpdklab
2023-02-10 14:11 dpdklab
2023-02-10 14:11 dpdklab
2023-02-10 14:15 dpdklab
2023-02-10 14:22 dpdklab
2023-02-10 14:23 dpdklab
2023-02-10 14:31 dpdklab
2023-02-10 14:35 dpdklab
2023-02-10 14:35 dpdklab
2023-02-12 1:38 dpdklab
2023-02-12 13:03 dpdklab
2023-02-12 20:03 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=202302090722.3197M0Ir4074436@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).