From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126616 [PATCH v2] net/ixgbe: consider DCB/VMDq conf when getting RSS conf
Date: Fri, 28 Apr 2023 16:37:10 +0800 [thread overview]
Message-ID: <202304280837.33S8bA7A2908895@localhost.localdomain> (raw)
In-Reply-To: <20230428084257.3440913-1-zhoumin@loongson.cn>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126616
_Compilation OK_
Submitter: Min Zhou <zhoumin@loongson.cn>
Date: Fri, 28 Apr 2023 16:42:57 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 03e7b4ee3446f937e3b29d02889787e09d2e5bf4
126616 --> 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-04-28 8:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230428084257.3440913-1-zhoumin@loongson.cn>
2023-04-28 8:37 ` qemudev [this message]
2023-04-28 8:41 ` qemudev
2023-04-28 8:43 ` |WARNING| " checkpatch
2023-04-28 9:59 ` |SUCCESS| " 0-day Robot
2023-04-28 9:18 |SUCCESS| pw126616 [PATCH] [v2] " dpdklab
2023-04-28 9:19 dpdklab
2023-04-28 9:23 dpdklab
2023-04-28 9:24 dpdklab
2023-04-28 9:25 dpdklab
2023-04-28 9:25 dpdklab
2023-04-28 9:26 dpdklab
2023-04-28 9:29 dpdklab
2023-04-28 9:38 dpdklab
2023-04-28 9:41 dpdklab
2023-04-28 9:44 dpdklab
2023-04-28 9:45 dpdklab
2023-04-28 9:47 dpdklab
2023-04-28 9:48 dpdklab
2023-04-28 9:49 dpdklab
2023-04-28 9:50 dpdklab
2023-04-28 9:51 dpdklab
2023-04-28 10:01 dpdklab
2023-04-28 10:03 dpdklab
2023-04-28 10:03 dpdklab
2023-04-28 10:14 dpdklab
2023-04-28 14:59 dpdklab
2023-04-28 20:29 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=202304280837.33S8bA7A2908895@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).