From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw136304 [PATCH] net/cnxk: fix aged flows query
Date: Fri, 2 Feb 2024 12:59:26 +0800 [thread overview]
Message-ID: <202402020459.4124xQ8c2809261@localhost.localdomain> (raw)
In-Reply-To: <20240202052137.1324084-1-psatheesh@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/136304
_Compilation OK_
Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Fri, 2 Feb 2024 10:51:37 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: 7d3daa3988e6b0216ace4ad882f3ccf1664cc7a7
136304 --> 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:[~2024-02-02 5:24 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240202052137.1324084-1-psatheesh@marvell.com>
2024-02-02 4:59 ` qemudev [this message]
2024-02-02 5:03 ` qemudev
2024-02-02 5:22 ` checkpatch
2024-02-02 6:24 ` |SUCCESS| pw136304 [dpdk-dev] " 0-day Robot
2024-02-02 6:49 |SUCCESS| pw136304 " dpdklab
2024-02-02 6:51 dpdklab
2024-02-02 6:52 dpdklab
2024-02-02 6:53 dpdklab
2024-02-02 6:53 dpdklab
2024-02-02 6:54 dpdklab
2024-02-02 6:56 dpdklab
2024-02-02 6:56 dpdklab
2024-02-02 6:56 dpdklab
2024-02-02 6:58 dpdklab
2024-02-02 7:03 dpdklab
2024-02-02 7:07 dpdklab
2024-02-02 7:16 dpdklab
2024-02-02 7:21 dpdklab
2024-02-02 7:25 dpdklab
2024-02-02 7:27 dpdklab
2024-02-02 7:47 dpdklab
2024-02-02 7:57 dpdklab
2024-02-02 8:14 dpdklab
2024-02-02 8:34 dpdklab
2024-02-02 8:37 dpdklab
2024-02-02 8:39 dpdklab
2024-02-02 8:43 dpdklab
2024-02-02 8:44 dpdklab
2024-02-02 8:52 dpdklab
2024-02-02 8:54 dpdklab
2024-02-02 8:54 dpdklab
2024-02-02 8:55 dpdklab
2024-02-02 8:56 dpdklab
2024-02-02 8:59 dpdklab
2024-02-02 9:00 dpdklab
2024-02-02 9:01 dpdklab
2024-02-02 9:01 dpdklab
2024-02-02 9:02 dpdklab
2024-02-02 9:03 dpdklab
2024-02-02 9:03 dpdklab
2024-02-02 9:04 dpdklab
2024-02-02 9:05 dpdklab
2024-02-02 9:05 dpdklab
2024-02-02 9:05 dpdklab
2024-02-02 9:06 dpdklab
2024-02-02 9:06 dpdklab
2024-02-02 9:07 dpdklab
2024-02-02 9:08 dpdklab
2024-02-02 9:08 dpdklab
2024-02-02 9:09 dpdklab
2024-02-02 9:09 dpdklab
2024-02-02 9:14 dpdklab
2024-02-02 9:15 dpdklab
2024-02-02 9:16 dpdklab
2024-02-02 9:17 dpdklab
2024-02-02 9:18 dpdklab
2024-02-02 9:18 dpdklab
2024-02-02 9:23 dpdklab
2024-02-02 9:23 dpdklab
2024-02-02 9:23 dpdklab
2024-02-02 9:23 dpdklab
2024-02-02 9:24 dpdklab
2024-02-02 9:24 dpdklab
2024-02-02 9:25 dpdklab
2024-02-02 9:32 dpdklab
2024-02-02 9:32 dpdklab
2024-02-02 9:34 dpdklab
2024-02-02 9:36 dpdklab
2024-02-02 9:55 dpdklab
2024-02-02 9:55 dpdklab
2024-02-02 12:09 dpdklab
2024-02-02 12:39 dpdklab
2024-02-02 13:13 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=202402020459.4124xQ8c2809261@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).