From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148295 [PATCH] bus/fslmc: fix bus scan return failure value
Date: Mon, 11 Nov 2024 17:55:08 +0800 [thread overview]
Message-ID: <202411110955.4AB9t8Yq769568@localhost.localdomain> (raw)
In-Reply-To: <20241111102607.1571897-1-hemant.agrawal@nxp.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148295
_Compilation OK_
Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Mon, 11 Nov 2024 15:56:07 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: f30a1bbd63f494f5ba623582d7e9166c817794a4
148295 --> 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-11-11 10:28 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241111102607.1571897-1-hemant.agrawal@nxp.com>
2024-11-11 9:55 ` qemudev [this message]
2024-11-11 9:59 ` qemudev
2024-11-11 10:26 ` checkpatch
2024-11-11 12:27 ` |SUCCESS| pw148295 [PATCH] bus/fslmc: fix bus scan return failure va dpdklab
2024-11-11 12:41 ` dpdklab
2024-11-11 12:45 ` dpdklab
2024-11-11 12:47 ` dpdklab
2024-11-11 12:52 ` dpdklab
2024-11-11 12:58 ` dpdklab
2024-11-11 13:02 ` dpdklab
2024-11-11 13:16 ` dpdklab
2024-11-11 13:18 ` dpdklab
2024-11-11 13:21 ` dpdklab
2024-11-11 13:24 ` dpdklab
2024-11-11 13:32 ` dpdklab
2024-11-11 13:32 ` dpdklab
2024-11-11 13:37 ` dpdklab
2024-11-11 13:38 ` dpdklab
2024-11-11 13:50 ` |PENDING| " dpdklab
2024-11-11 13:55 ` dpdklab
2024-11-11 13:57 ` |SUCCESS| " dpdklab
2024-11-11 14:05 ` dpdklab
2024-11-11 14:13 ` |PENDING| " dpdklab
2024-11-11 14:24 ` |SUCCESS| " dpdklab
2024-11-11 14:34 ` dpdklab
2024-11-11 14:37 ` dpdklab
2024-11-11 14:42 ` |PENDING| " dpdklab
2024-11-11 14:45 ` |SUCCESS| " dpdklab
2024-11-11 14:47 ` dpdklab
2024-11-11 15:03 ` dpdklab
2024-11-11 15:06 ` |WARNING| " dpdklab
2024-11-11 15:16 ` |SUCCESS| " dpdklab
2024-11-11 15:44 ` |WARNING| " dpdklab
2024-11-11 15:53 ` |SUCCESS| " dpdklab
2024-11-11 16:21 ` dpdklab
2024-11-11 16:28 ` |WARNING| " dpdklab
2024-11-11 16:36 ` |SUCCESS| " dpdklab
2024-11-11 17:03 ` |WARNING| " dpdklab
2024-11-11 17:09 ` |SUCCESS| " dpdklab
2024-11-11 17:16 ` dpdklab
2024-11-11 17:16 ` |WARNING| " dpdklab
2024-11-11 19:06 ` dpdklab
2024-11-11 19:16 ` |SUCCESS| " dpdklab
2024-11-11 19:21 ` |WARNING| " dpdklab
2024-11-11 19:52 ` dpdklab
2024-11-11 20:07 ` dpdklab
2024-11-11 21:37 ` |SUCCESS| " dpdklab
2024-11-11 22:06 ` 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=202411110955.4AB9t8Yq769568@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).