From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124084-124083 [PATCH v11 3/3] net/cnxk: skip red drop for ingress policer
Date: Thu, 16 Feb 2023 22:42:12 +0800 [thread overview]
Message-ID: <202302161442.31GEgCYd1678473@localhost.localdomain> (raw)
In-Reply-To: <20230216145128.1734257-3-rkudurumalla@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124083
_Compilation OK_
Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Thu, 16 Feb 2023 20:21:26 +0530
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: ad5c1562071512062028d9e58625545a6dee0493
124084-124083 --> 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-16 14:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230216145128.1734257-3-rkudurumalla@marvell.com>
2023-02-16 14:42 ` qemudev [this message]
2023-02-16 14:46 ` qemudev
2023-02-16 14:52 ` |SUCCESS| pw124083 " checkpatch
2023-02-16 16:59 ` 0-day Robot
2023-02-16 15:29 |SUCCESS| pw124084-124083 [PATCH] [v11, " dpdklab
2023-02-16 15:31 dpdklab
2023-02-16 15:34 dpdklab
2023-02-16 15:35 dpdklab
2023-02-16 15:46 dpdklab
2023-02-16 19:22 dpdklab
2023-02-16 19:34 dpdklab
2023-02-16 19:40 dpdklab
2023-02-16 19:51 dpdklab
2023-02-16 19:53 dpdklab
2023-02-16 19:53 dpdklab
2023-02-16 19:56 dpdklab
2023-02-16 20:06 dpdklab
2023-02-16 20:07 dpdklab
2023-02-16 20:21 dpdklab
2023-02-16 20:25 dpdklab
2023-02-16 20:29 dpdklab
2023-02-16 20:32 dpdklab
2023-02-16 20:32 dpdklab
2023-02-18 1:46 dpdklab
2023-02-19 12:11 dpdklab
2023-02-24 23:11 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=202302161442.31GEgCYd1678473@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).