From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123666-123669 [PATCH v6 3/3] net/cnxk: skip red drop for ingress policer
Date: Fri, 10 Feb 2023 16:18:58 +0800 [thread overview]
Message-ID: <202302100818.31A8IwrR1423230@localhost.localdomain> (raw)
In-Reply-To: <20230210082623.1005496-3-rkudurumalla@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123669
_Compilation OK_
Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Fri, 10 Feb 2023 13:56:21 +0530
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 4e43e585794e446dc405f7791e3534ea3bff31ff
123666-123669 --> 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-10 8:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230210082623.1005496-3-rkudurumalla@marvell.com>
2023-02-10 8:18 ` qemudev [this message]
2023-02-10 8:22 ` qemudev
2023-02-10 8:27 ` |SUCCESS| pw123669 " checkpatch
2023-02-10 8:59 |SUCCESS| pw123666-123669 [PATCH] [v6, " dpdklab
2023-02-10 9:05 dpdklab
2023-02-10 9:06 dpdklab
2023-02-10 9:06 dpdklab
2023-02-10 9:07 dpdklab
2023-02-10 9:12 dpdklab
2023-02-10 9:15 dpdklab
2023-02-10 9:15 dpdklab
2023-02-10 9:15 dpdklab
2023-02-10 9:17 dpdklab
2023-02-10 9:22 dpdklab
2023-02-10 9:32 dpdklab
2023-02-10 10:41 dpdklab
2023-02-11 22:31 dpdklab
2023-02-11 22:31 dpdklab
2023-02-11 22:39 dpdklab
2023-02-11 22:46 dpdklab
2023-02-11 22:56 dpdklab
2023-02-11 23:00 dpdklab
2023-02-11 23:02 dpdklab
2023-02-11 23:03 dpdklab
2023-02-11 23:05 dpdklab
2023-02-11 23:08 dpdklab
2023-02-11 23:13 dpdklab
2023-02-11 23:18 dpdklab
2023-02-11 23:22 dpdklab
2023-02-11 23:22 dpdklab
2023-02-12 22:01 dpdklab
2023-02-13 11:05 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=202302100818.31A8IwrR1423230@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).