From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw149307 [PATCH 1/1] net/{octeon_ep, enetfec}: remove unused value
Date: Thu, 19 Dec 2024 03:33:11 +0800 [thread overview]
Message-ID: <202412181933.4BIJXBSi2597189@localhost.localdomain> (raw)
In-Reply-To: <20241218200306.546714-2-otilibil@eurecom.fr>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/149307
_Compilation OK_
Submitter: Ariel Otilibili <otilibil@eurecom.fr>
Date: Wed, 18 Dec 2024 21:00:09 +0100
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 78d0246a2e2fb14cba220d507192d12d2ce896ac
149307 --> 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-18 20:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241218200306.546714-2-otilibil@eurecom.fr>
2024-12-18 19:33 ` qemudev [this message]
2024-12-18 19:37 ` qemudev
2024-12-18 20:04 ` checkpatch
2024-12-18 21:43 ` 0-day Robot
2024-12-18 22:14 ` |SUCCESS| pw149307 [PATCH] [1/1] net/{octeon_ep,enetfec}: remove unu dpdklab
2024-12-18 22:15 ` dpdklab
2024-12-18 22:24 ` dpdklab
2024-12-18 22:34 ` dpdklab
2024-12-18 22:37 ` dpdklab
2024-12-18 22:38 ` dpdklab
2024-12-18 22:40 ` dpdklab
2024-12-18 22:43 ` dpdklab
2024-12-18 22:59 ` dpdklab
2024-12-18 23:20 ` |PENDING| " dpdklab
2024-12-18 23:24 ` |WARNING| " dpdklab
2024-12-18 23:24 ` dpdklab
2024-12-18 23:26 ` dpdklab
2024-12-18 23:37 ` |SUCCESS| " dpdklab
2024-12-19 0:34 ` dpdklab
2024-12-19 0:43 ` dpdklab
2024-12-19 0:46 ` |WARNING| " dpdklab
2024-12-19 1:22 ` |SUCCESS| " dpdklab
2024-12-19 3:52 ` dpdklab
2024-12-19 4:26 ` |WARNING| " dpdklab
2024-12-19 4: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=202412181933.4BIJXBSi2597189@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).