From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120399-120400 [PATCH 2/2] net/cnxk: add validate flag for RTE flow for cnxk
Date: Thu, 1 Dec 2022 12:11:57 +0800 [thread overview]
Message-ID: <202212010411.2B14Bvrr3715121@localhost.localdomain> (raw)
In-Reply-To: <20221201042011.2977887-2-psatheesh@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/120400
_Compilation OK_
Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Thu, 1 Dec 2022 09:50:10 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: f262f16087ea6a77357a915cf4c0d10ddc7b6562
120399-120400 --> 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:[~2022-12-01 4:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221201042011.2977887-2-psatheesh@marvell.com>
2022-12-01 4:11 ` qemudev [this message]
2022-12-01 4:15 ` qemudev
2022-12-01 4:22 ` |SUCCESS| pw120400 " checkpatch
2022-12-01 6:38 ` |SUCCESS| pw120400 [dpdk-dev] " 0-day Robot
2022-12-01 5:13 |SUCCESS| pw120399-120400 [PATCH] [2/2] " dpdklab
2022-12-01 5:16 dpdklab
2022-12-01 5:24 dpdklab
2022-12-01 5:25 dpdklab
2022-12-01 5:32 dpdklab
2022-12-01 5:44 dpdklab
2022-12-01 6:39 dpdklab
2022-12-01 7:32 dpdklab
2022-12-02 21:41 dpdklab
2022-12-02 22:24 dpdklab
2022-12-02 22:25 dpdklab
2022-12-02 22:25 dpdklab
2022-12-02 22:25 dpdklab
2022-12-02 22:26 dpdklab
2022-12-02 22:26 dpdklab
2022-12-02 22:26 dpdklab
2022-12-02 22:27 dpdklab
2022-12-02 22:27 dpdklab
2022-12-03 11:06 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=202212010411.2B14Bvrr3715121@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).