From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139079 [PATCH] net/fm10k: fix cleanup during init failure
Date: Wed, 3 Apr 2024 19:33:49 +0800 [thread overview]
Message-ID: <202404031133.433BXn521546562@localhost.localdomain> (raw)
In-Reply-To: <20240403115541.2369-1-julien.meunier@nokia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139079
_Compilation OK_
Submitter: Julien Meunier <julien.meunier@nokia.com>
Date: Wed, 3 Apr 2024 13:55:41 +0200
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 2c54ea7a59dfc0a819d3527309c62846fc8853af
139079 --> 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-03 11:58 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240403115541.2369-1-julien.meunier@nokia.com>
2024-04-03 11:33 ` qemudev [this message]
2024-04-03 11:38 ` qemudev
2024-04-03 11:56 ` checkpatch
2024-04-03 12:35 ` |FAILURE| pw139079 [PATCH] net/fm10k: fix cleanup during init failur dpdklab
2024-04-03 12:35 ` |SUCCESS| " dpdklab
2024-04-03 12:36 ` dpdklab
2024-04-03 12:36 ` dpdklab
2024-04-03 12:36 ` dpdklab
2024-04-03 12:36 ` dpdklab
2024-04-03 12:37 ` dpdklab
2024-04-03 12:37 ` dpdklab
2024-04-03 12:37 ` dpdklab
2024-04-03 12:37 ` dpdklab
2024-04-03 12:37 ` dpdklab
2024-04-03 12:38 ` dpdklab
2024-04-03 12:38 ` dpdklab
2024-04-03 12:38 ` dpdklab
2024-04-03 12:38 ` dpdklab
2024-04-03 12:38 ` dpdklab
2024-04-03 12:39 ` dpdklab
2024-04-03 12:39 ` dpdklab
2024-04-03 12:39 ` dpdklab
2024-04-03 12:41 ` dpdklab
2024-04-03 12:42 ` dpdklab
2024-04-03 12:42 ` dpdklab
2024-04-03 12:42 ` dpdklab
2024-04-03 12:42 ` dpdklab
2024-04-03 12:43 ` dpdklab
2024-04-03 12:43 ` dpdklab
2024-04-03 12:43 ` dpdklab
2024-04-03 12:44 ` dpdklab
2024-04-03 12:44 ` dpdklab
2024-04-03 12:45 ` dpdklab
2024-04-03 12:45 ` |FAILURE| " dpdklab
2024-04-03 12:45 ` |SUCCESS| pw139079 [PATCH] net/fm10k: fix cleanup during init failure 0-day Robot
2024-04-03 12:46 ` |SUCCESS| pw139079 [PATCH] net/fm10k: fix cleanup during init failur dpdklab
2024-04-03 12:46 ` dpdklab
2024-04-03 12:46 ` dpdklab
2024-04-03 12:47 ` dpdklab
2024-04-03 12:47 ` dpdklab
2024-04-03 12:47 ` dpdklab
2024-04-03 12:48 ` dpdklab
2024-04-03 12:48 ` dpdklab
2024-04-03 12:49 ` |FAILURE| " dpdklab
2024-04-03 12:50 ` |SUCCESS| " dpdklab
2024-04-03 12:50 ` dpdklab
2024-04-03 12:50 ` dpdklab
2024-04-03 12:50 ` dpdklab
2024-04-03 12:50 ` dpdklab
2024-04-03 12:51 ` dpdklab
2024-04-03 12:52 ` dpdklab
2024-04-03 12:52 ` dpdklab
2024-04-03 13:06 ` dpdklab
2024-04-03 13:06 ` dpdklab
2024-04-03 13:06 ` |FAILURE| " dpdklab
2024-04-03 13:07 ` dpdklab
2024-04-03 13:07 ` dpdklab
2024-04-03 13:08 ` |SUCCESS| " dpdklab
2024-04-03 13:08 ` dpdklab
2024-04-03 13:08 ` dpdklab
2024-04-03 13:23 ` dpdklab
2024-04-03 13:24 ` |FAILURE| " dpdklab
2024-04-03 13:33 ` |SUCCESS| " dpdklab
2024-04-03 13:34 ` dpdklab
2024-04-03 13:34 ` dpdklab
2024-04-03 13:34 ` |FAILURE| " dpdklab
2024-04-03 13:35 ` |SUCCESS| " dpdklab
2024-04-03 13:35 ` dpdklab
2024-04-03 13:36 ` |FAILURE| " dpdklab
2024-04-03 13:37 ` dpdklab
2024-04-03 13:38 ` |SUCCESS| " dpdklab
2024-04-03 13:39 ` |FAILURE| " dpdklab
2024-04-03 13:40 ` |SUCCESS| " dpdklab
2024-04-03 13:41 ` |FAILURE| " dpdklab
2024-04-03 13:41 ` dpdklab
2024-04-03 13:43 ` dpdklab
2024-04-03 13:43 ` |SUCCESS| " dpdklab
2024-04-03 13:43 ` |FAILURE| " dpdklab
2024-04-03 13:43 ` dpdklab
2024-04-03 13:44 ` |SUCCESS| " dpdklab
2024-04-03 13:47 ` dpdklab
2024-04-03 13:47 ` dpdklab
2024-04-03 13:47 ` |FAILURE| " dpdklab
2024-04-03 14:04 ` |SUCCESS| " dpdklab
2024-04-03 15:41 ` dpdklab
2024-04-03 15:50 ` dpdklab
2024-04-03 16:30 ` dpdklab
2024-04-04 6:50 ` dpdklab
2024-04-04 6:54 ` dpdklab
2024-04-04 6:58 ` |FAILURE| " dpdklab
2024-04-04 7:02 ` |SUCCESS| " dpdklab
2024-04-04 7:21 ` |FAILURE| " dpdklab
2024-04-05 15:38 ` |SUCCESS| " dpdklab
2024-04-05 15:53 ` dpdklab
2024-04-05 15:53 ` dpdklab
2024-04-05 15:54 ` dpdklab
2024-04-05 15:56 ` dpdklab
2024-04-05 15:58 ` dpdklab
2024-04-05 16:08 ` dpdklab
2024-04-05 16:21 ` dpdklab
2024-04-05 16:28 ` dpdklab
2024-04-05 16:32 ` dpdklab
2024-04-05 16:52 ` dpdklab
2024-04-05 16:56 ` dpdklab
2024-04-05 18:09 ` dpdklab
2024-04-05 21:28 ` 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=202404031133.433BXn521546562@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).