From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw145303 [PATCH v2] drivers: fix build issues with redundant newline changes
Date: Mon, 7 Oct 2024 20:14:22 +0800 [thread overview]
Message-ID: <202410071214.497CEML12615123@localhost.localdomain> (raw)
In-Reply-To: <20241007124110.1020548-1-jerinj@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/145303
_Compilation OK_
Submitter: Jerin Jacob <jerinj@marvell.com>
Date: Mon, 7 Oct 2024 18:11:10 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: 9a723449a5b30626db66bb27cd96834261d11971
145303 --> 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-10-07 12:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241007124110.1020548-1-jerinj@marvell.com>
2024-10-07 12:14 ` qemudev [this message]
2024-10-07 12:18 ` qemudev
2024-10-07 12:42 ` checkpatch
2024-10-07 13:44 ` |SUCCESS| pw145303 [dpdk-dev] " 0-day Robot
2024-10-07 16:33 ` |SUCCESS| pw145303 [PATCH] [v2] drivers: fix build issues with redun dpdklab
2024-10-07 16:37 ` dpdklab
2024-10-07 16:38 ` dpdklab
2024-10-07 16:40 ` dpdklab
2024-10-07 16:50 ` dpdklab
2024-10-07 17:02 ` dpdklab
2024-10-07 17:04 ` dpdklab
2024-10-07 17:10 ` dpdklab
2024-10-07 17:30 ` dpdklab
2024-10-07 17:38 ` dpdklab
2024-10-07 17:47 ` |PENDING| " dpdklab
2024-10-07 17:53 ` |SUCCESS| " dpdklab
2024-10-07 18:31 ` dpdklab
2024-10-07 18:32 ` |PENDING| " dpdklab
2024-10-07 18:56 ` dpdklab
2024-10-07 20:07 ` |SUCCESS| " dpdklab
2024-10-07 20:37 ` |PENDING| " dpdklab
2024-10-07 21:32 ` |SUCCESS| " dpdklab
2024-10-07 22:42 ` dpdklab
2024-10-08 0:51 ` dpdklab
2024-10-08 0:57 ` dpdklab
2024-10-08 3:20 ` 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=202410071214.497CEML12615123@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).