From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148032-148031 [PATCH 2/2] net/hns3: fix cannot fully use hardware flow director table
Date: Thu, 7 Nov 2024 19:37:12 +0800 [thread overview]
Message-ID: <202411071137.4A7BbCBD1314130@localhost.localdomain> (raw)
In-Reply-To: <20241107115645.22617-3-haijie1@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148031
_Compilation OK_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Thu, 7 Nov 2024 19:56:44 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 43f5dad89c4fcc967988c8f60011136928e49428
148032-148031 --> 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-11-07 12:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241107115645.22617-3-haijie1@huawei.com>
2024-11-07 11:37 ` qemudev [this message]
2024-11-07 11:41 ` qemudev
2024-11-07 12:08 ` |SUCCESS| pw148031 " checkpatch
2024-11-07 12:49 ` |PENDING| pw148032-148031 [PATCH] [2/2] net/hns3: fix cannot fully u dpdklab
2024-11-07 12:51 ` |SUCCESS| " dpdklab
2024-11-07 12:52 ` |PENDING| " dpdklab
2024-11-07 12:53 ` |SUCCESS| " dpdklab
2024-11-07 12:55 ` |PENDING| " dpdklab
2024-11-07 13:03 ` |SUCCESS| " dpdklab
2024-11-07 13:05 ` dpdklab
2024-11-07 13:06 ` dpdklab
2024-11-07 13:06 ` dpdklab
2024-11-07 13:09 ` dpdklab
2024-11-07 13:14 ` |SUCCESS| pw148031 [PATCH 2/2] net/hns3: fix cannot fully use hardware flow director table 0-day Robot
2024-11-07 13:28 ` |SUCCESS| pw148032-148031 [PATCH] [2/2] net/hns3: fix cannot fully u dpdklab
2024-11-07 13:29 ` dpdklab
2024-11-07 13:31 ` dpdklab
2024-11-07 13:32 ` dpdklab
2024-11-07 14:05 ` dpdklab
2024-11-07 14:27 ` dpdklab
2024-11-07 14:56 ` 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=202411071137.4A7BbCBD1314130@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).