From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139218 [PATCH] net/cnxk: add RSS config via ethdev configure API
Date: Wed, 10 Apr 2024 20:53:08 +0800 [thread overview]
Message-ID: <202404101253.43ACr8wJ404944@localhost.localdomain> (raw)
In-Reply-To: <20240410131127.2482240-1-skori@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139218
_Compilation OK_
Submitter: Sunil Kumar Kori <skori@marvell.com>
Date: Wed, 10 Apr 2024 18:41:27 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139218 --> 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-04-10 13:18 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240410131127.2482240-1-skori@marvell.com>
2024-04-10 12:53 ` qemudev [this message]
2024-04-10 12:57 ` qemudev
2024-04-10 13:12 ` checkpatch
2024-04-10 14:01 ` |SUCCESS| pw139218 [PATCH] net/cnxk: add RSS config via ethdev confi dpdklab
2024-04-10 14:01 ` dpdklab
2024-04-10 14:04 ` |SUCCESS| pw139218 [PATCH] net/cnxk: add RSS config via ethdev configure API 0-day Robot
2024-04-10 14:06 ` |SUCCESS| pw139218 [PATCH] net/cnxk: add RSS config via ethdev confi dpdklab
2024-04-10 14:06 ` dpdklab
2024-04-10 14:07 ` dpdklab
2024-04-10 14:07 ` dpdklab
2024-04-10 14:07 ` dpdklab
2024-04-10 14:08 ` dpdklab
2024-04-10 14:08 ` dpdklab
2024-04-10 14:08 ` dpdklab
2024-04-10 14:08 ` dpdklab
2024-04-10 14:09 ` dpdklab
2024-04-10 14:09 ` dpdklab
2024-04-10 14:09 ` dpdklab
2024-04-10 14:10 ` dpdklab
2024-04-10 14:10 ` dpdklab
2024-04-10 14:10 ` dpdklab
2024-04-10 14:10 ` dpdklab
2024-04-10 14:11 ` dpdklab
2024-04-10 14:11 ` dpdklab
2024-04-10 14:11 ` dpdklab
2024-04-10 14:12 ` dpdklab
2024-04-10 14:15 ` dpdklab
2024-04-10 14:15 ` dpdklab
2024-04-10 14:15 ` dpdklab
2024-04-10 14:15 ` dpdklab
2024-04-10 14:15 ` dpdklab
2024-04-10 14:16 ` dpdklab
2024-04-10 14:16 ` dpdklab
2024-04-10 14:16 ` dpdklab
2024-04-10 14:17 ` dpdklab
2024-04-10 14:17 ` dpdklab
2024-04-10 14:17 ` dpdklab
2024-04-10 14:18 ` dpdklab
2024-04-10 14:18 ` dpdklab
2024-04-10 14:18 ` dpdklab
2024-04-10 14:18 ` dpdklab
2024-04-10 14:18 ` dpdklab
2024-04-10 14:19 ` dpdklab
2024-04-10 14:19 ` dpdklab
2024-04-10 14:21 ` dpdklab
2024-04-10 14:22 ` dpdklab
2024-04-10 14:22 ` dpdklab
2024-04-10 14:22 ` dpdklab
2024-04-10 14:22 ` dpdklab
2024-04-10 14:22 ` dpdklab
2024-04-10 14:22 ` dpdklab
2024-04-10 14:23 ` dpdklab
2024-04-10 14:23 ` dpdklab
2024-04-10 14:23 ` dpdklab
2024-04-10 14:32 ` dpdklab
2024-04-10 14:32 ` dpdklab
2024-04-10 14:34 ` dpdklab
2024-04-10 14:35 ` dpdklab
2024-04-10 14:39 ` dpdklab
2024-04-10 14:39 ` dpdklab
2024-04-10 14:40 ` dpdklab
2024-04-10 14:40 ` dpdklab
2024-04-10 14:40 ` dpdklab
2024-04-10 14:40 ` dpdklab
2024-04-10 14:41 ` dpdklab
2024-04-10 14:41 ` dpdklab
2024-04-10 14:41 ` dpdklab
2024-04-10 14:42 ` dpdklab
2024-04-10 14:42 ` dpdklab
2024-04-10 14:43 ` dpdklab
2024-04-10 14:43 ` dpdklab
2024-04-10 14:44 ` dpdklab
2024-04-10 14:44 ` dpdklab
2024-04-10 14:45 ` dpdklab
2024-04-10 14:45 ` dpdklab
2024-04-10 14:46 ` dpdklab
2024-04-10 14:46 ` dpdklab
2024-04-10 14:46 ` dpdklab
2024-04-10 14:46 ` dpdklab
2024-04-10 14:46 ` dpdklab
2024-04-10 14:47 ` dpdklab
2024-04-10 14:49 ` dpdklab
2024-04-10 14:50 ` dpdklab
2024-04-10 14:51 ` dpdklab
2024-04-10 14:55 ` dpdklab
2024-04-10 14:58 ` dpdklab
2024-04-10 15:01 ` dpdklab
2024-04-10 15:01 ` dpdklab
2024-04-10 15:03 ` dpdklab
2024-04-10 15:05 ` dpdklab
2024-04-10 15:17 ` dpdklab
2024-04-10 16:46 ` 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=202404101253.43ACr8wJ404944@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).