From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139494 [PATCH] net/ixgbe: don't create a delayed interrupt handler if one already exists
Date: Thu, 18 Apr 2024 21:31:21 +0800 [thread overview]
Message-ID: <202404181331.43IDVLXc1713657@localhost.localdomain> (raw)
In-Reply-To: <20240418135307.3270094-1-edwin.brossette@6wind.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139494
_Compilation OK_
Submitter: edwin.brossette@6wind.com
Date: Thu, 18 Apr 2024 15:53:07 +0200
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 2ac57ed414af92f0c30a799e1824fd47f86a94b0
139494 --> 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-18 13:56 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240418135307.3270094-1-edwin.brossette@6wind.com>
2024-04-18 13:31 ` qemudev [this message]
2024-04-18 13:35 ` qemudev
2024-04-18 13:54 ` |WARNING| " checkpatch
2024-04-18 14:46 ` |FAILURE| " 0-day Robot
2024-04-18 14:57 ` |SUCCESS| pw139494 [PATCH] net/ixgbe: don't create a delayed interru dpdklab
2024-04-18 14:57 ` dpdklab
2024-04-18 14:58 ` dpdklab
2024-04-18 14:58 ` dpdklab
2024-04-18 14:58 ` dpdklab
2024-04-18 14:58 ` dpdklab
2024-04-18 14:59 ` dpdklab
2024-04-18 14:59 ` dpdklab
2024-04-18 14:59 ` dpdklab
2024-04-18 14:59 ` dpdklab
2024-04-18 15:00 ` dpdklab
2024-04-18 15:00 ` dpdklab
2024-04-18 15:00 ` dpdklab
2024-04-18 15:00 ` dpdklab
2024-04-18 15:00 ` dpdklab
2024-04-18 15:00 ` dpdklab
2024-04-18 15:01 ` dpdklab
2024-04-18 15:01 ` dpdklab
2024-04-18 15:02 ` dpdklab
2024-04-18 15:02 ` dpdklab
2024-04-18 15:02 ` dpdklab
2024-04-18 15:02 ` dpdklab
2024-04-18 15:03 ` dpdklab
2024-04-18 15:03 ` dpdklab
2024-04-18 15:03 ` dpdklab
2024-04-18 15:03 ` dpdklab
2024-04-18 15:04 ` dpdklab
2024-04-18 15:04 ` dpdklab
2024-04-18 15:04 ` dpdklab
2024-04-18 15:04 ` dpdklab
2024-04-18 15:04 ` dpdklab
2024-04-18 15:04 ` dpdklab
2024-04-18 15:04 ` dpdklab
2024-04-18 15:05 ` dpdklab
2024-04-18 15:05 ` dpdklab
2024-04-18 15:05 ` dpdklab
2024-04-18 15:05 ` dpdklab
2024-04-18 15:05 ` dpdklab
2024-04-18 15:05 ` dpdklab
2024-04-18 15:06 ` dpdklab
2024-04-18 15:06 ` dpdklab
2024-04-18 15:06 ` dpdklab
2024-04-18 15:06 ` dpdklab
2024-04-18 15:06 ` dpdklab
2024-04-18 15:06 ` dpdklab
2024-04-18 15:06 ` dpdklab
2024-04-18 15:07 ` dpdklab
2024-04-18 15:07 ` dpdklab
2024-04-18 15:07 ` dpdklab
2024-04-18 15:07 ` dpdklab
2024-04-18 15:08 ` dpdklab
2024-04-18 15:08 ` dpdklab
2024-04-18 15:08 ` dpdklab
2024-04-18 15:09 ` dpdklab
2024-04-18 15:09 ` dpdklab
2024-04-18 15:09 ` dpdklab
2024-04-18 15:10 ` dpdklab
2024-04-18 15:10 ` dpdklab
2024-04-18 15:10 ` dpdklab
2024-04-18 15:10 ` dpdklab
2024-04-18 15:10 ` dpdklab
2024-04-18 15:11 ` dpdklab
2024-04-18 15:11 ` dpdklab
2024-04-18 15:11 ` dpdklab
2024-04-18 15:12 ` dpdklab
2024-04-18 15:12 ` dpdklab
2024-04-18 15:13 ` dpdklab
2024-04-18 15:15 ` dpdklab
2024-04-18 15:17 ` dpdklab
2024-04-18 15:17 ` dpdklab
2024-04-18 15:21 ` dpdklab
2024-04-18 15:22 ` dpdklab
2024-04-18 15:46 ` dpdklab
2024-04-18 15:56 ` dpdklab
2024-04-18 15:59 ` dpdklab
2024-04-18 16:00 ` dpdklab
2024-04-18 16:08 ` dpdklab
2024-04-18 16:15 ` dpdklab
2024-04-18 17:11 ` dpdklab
2024-04-18 17:14 ` dpdklab
2024-04-18 17:17 ` dpdklab
2024-04-18 17:32 ` dpdklab
2024-04-18 17:36 ` dpdklab
2024-04-18 17:55 ` dpdklab
2024-04-18 20:26 ` dpdklab
2024-04-18 21:30 ` 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=202404181331.43IDVLXc1713657@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).