From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw149472 [PATCH v3] net/bonding: fix dedicated queue setup failed
Date: Thu, 26 Dec 2024 08:58:25 +0800 [thread overview]
Message-ID: <202412260058.4BQ0wP6l1551426@localhost.localdomain> (raw)
In-Reply-To: <20241226012618.13535-1-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/149472
_Compilation OK_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Thu, 26 Dec 2024 09:26:18 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 94ad302b4ebba4a5b6706a1c43ea0505e5098169
149472 --> 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-12-26 1:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241226012618.13535-1-chaoyong.he@corigine.com>
2024-12-26 0:58 ` qemudev [this message]
2024-12-26 1:03 ` qemudev
2024-12-26 1:27 ` checkpatch
2024-12-26 2:15 ` |PENDING| pw149472 [PATCH] [v3] net/bonding: fix dedicated queue set dpdklab
2024-12-26 2:16 ` dpdklab
2024-12-26 2:18 ` |SUCCESS| " dpdklab
2024-12-26 2:23 ` |PENDING| " dpdklab
2024-12-26 2:24 ` |SUCCESS| pw149472 [PATCH v3] net/bonding: fix dedicated queue setup failed 0-day Robot
2024-12-26 2:26 ` |SUCCESS| pw149472 [PATCH] [v3] net/bonding: fix dedicated queue set dpdklab
2024-12-26 2:27 ` dpdklab
2024-12-26 2:32 ` dpdklab
2024-12-26 2:35 ` dpdklab
2024-12-26 2:42 ` dpdklab
2024-12-26 2:43 ` dpdklab
2024-12-26 2:43 ` dpdklab
2024-12-26 2:44 ` dpdklab
2024-12-26 2:46 ` |WARNING| " dpdklab
2024-12-26 2:47 ` dpdklab
2024-12-26 2:49 ` |SUCCESS| " dpdklab
2024-12-26 2:54 ` dpdklab
2024-12-26 3:06 ` |WARNING| " dpdklab
2024-12-26 3:13 ` |SUCCESS| " dpdklab
2024-12-26 3: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=202412260058.4BQ0wP6l1551426@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).