From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw127640 [PATCH v2] ethdev: add indirect list METER_MARK flow update structure
Date: Mon, 29 May 2023 09:32:31 +0800 [thread overview]
Message-ID: <202305290132.34T1WV6q2228869@localhost.localdomain> (raw)
In-Reply-To: <20230528161245.72317-1-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/127640
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Sun, 28 May 2023 19:12:45 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 7c7bfb93f11155cfcacde2372c3eaa5b0635b63f
127640 --> 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 prev parent reply other threads:[~2023-05-29 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230528161245.72317-1-getelson@nvidia.com>
2023-05-28 16:13 ` checkpatch
2023-05-29 1:32 ` qemudev [this message]
2023-05-29 1:36 ` qemudev
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=202305290132.34T1WV6q2228869@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).