From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138764 [PATCH] net/ixgbe: add param check when tx_queue or rx_queqe is null
Date: Mon, 25 Mar 2024 15:32:45 +0800 [thread overview]
Message-ID: <202403250732.42P7Wjal2259744@localhost.localdomain> (raw)
In-Reply-To: <20240323144842.12331-1-keivinwang@126.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138764
_Compilation OK_
Submitter: keivinwang <keivinwang@126.com>
Date: Sat, 23 Mar 2024 22:48:42 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 2c54ea7a59dfc0a819d3527309c62846fc8853af
138764 --> 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-03-25 7:57 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240323144842.12331-1-keivinwang@126.com>
2024-03-25 7:32 ` qemudev [this message]
2024-03-25 7:37 ` qemudev
2024-03-25 7:55 ` checkpatch
2024-03-25 11:22 ` |SUCCESS| pw138764 [PATCH] net/ixgbe: add param check when tx_queue dpdklab
2024-03-25 11:23 ` dpdklab
2024-03-25 11:23 ` dpdklab
2024-03-25 11:24 ` dpdklab
2024-03-25 11:25 ` dpdklab
2024-03-25 11:26 ` dpdklab
2024-03-25 11:26 ` dpdklab
2024-03-25 11:38 ` dpdklab
2024-03-25 11:38 ` dpdklab
2024-03-25 11:39 ` dpdklab
2024-03-25 11:40 ` |FAILURE| " dpdklab
2024-03-25 11:41 ` dpdklab
2024-03-25 11:42 ` |SUCCESS| " dpdklab
2024-03-25 11:43 ` |FAILURE| " dpdklab
2024-03-25 11:44 ` |SUCCESS| " dpdklab
2024-03-25 11:44 ` dpdklab
2024-03-25 11:44 ` dpdklab
2024-03-25 11:44 ` dpdklab
2024-03-25 11:44 ` dpdklab
2024-03-25 11:45 ` dpdklab
2024-03-25 11:45 ` dpdklab
2024-03-25 11:45 ` dpdklab
2024-03-25 11:45 ` dpdklab
2024-03-25 11:45 ` dpdklab
2024-03-25 11:46 ` dpdklab
2024-03-25 11:46 ` dpdklab
2024-03-25 11:46 ` dpdklab
2024-03-25 11:46 ` dpdklab
2024-03-25 11:47 ` dpdklab
2024-03-25 11:47 ` dpdklab
2024-03-25 11:47 ` dpdklab
2024-03-25 11:47 ` dpdklab
2024-03-25 11:47 ` dpdklab
2024-03-25 11:47 ` dpdklab
2024-03-25 11:48 ` dpdklab
2024-03-25 11:48 ` dpdklab
2024-03-25 11:48 ` dpdklab
2024-03-25 11:48 ` dpdklab
2024-03-25 11:48 ` dpdklab
2024-03-25 11:48 ` dpdklab
2024-03-25 11:49 ` dpdklab
2024-03-25 11:49 ` dpdklab
2024-03-25 11:49 ` dpdklab
2024-03-25 11:49 ` dpdklab
2024-03-25 11:49 ` dpdklab
2024-03-25 11:49 ` |FAILURE| " dpdklab
2024-03-25 11:50 ` |SUCCESS| " dpdklab
2024-03-25 11:51 ` dpdklab
2024-03-25 11:51 ` dpdklab
2024-03-25 11:51 ` dpdklab
2024-03-25 11:51 ` dpdklab
2024-03-25 11:52 ` dpdklab
2024-03-25 11:52 ` dpdklab
2024-03-25 11:52 ` dpdklab
2024-03-25 11:52 ` dpdklab
2024-03-25 11:52 ` dpdklab
2024-03-25 11:52 ` dpdklab
2024-03-25 11:53 ` dpdklab
2024-03-25 11:53 ` dpdklab
2024-03-25 11:54 ` dpdklab
2024-03-25 11:55 ` dpdklab
2024-03-25 11:55 ` dpdklab
2024-03-25 11:57 ` dpdklab
2024-03-25 11:58 ` dpdklab
2024-03-25 12:02 ` dpdklab
2024-03-25 12:02 ` dpdklab
2024-03-25 12:04 ` dpdklab
2024-03-25 12:04 ` dpdklab
2024-03-25 12:05 ` dpdklab
2024-03-25 12:09 ` dpdklab
2024-03-25 12:10 ` dpdklab
2024-03-25 12:13 ` dpdklab
2024-03-25 12:18 ` dpdklab
2024-03-25 12:19 ` dpdklab
2024-03-25 12:20 ` dpdklab
2024-03-25 12:35 ` dpdklab
2024-03-25 13:01 ` dpdklab
2024-03-25 14:01 ` dpdklab
2024-03-25 14:37 ` 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=202403250732.42P7Wjal2259744@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).