From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148712 [PATCH] net/bnxt: fix segmentation fault
Date: Thu, 21 Nov 2024 00:29:09 +0800 [thread overview]
Message-ID: <202411201629.4AKGT9OG117704@localhost.localdomain> (raw)
In-Reply-To: <20241120170058.18742-1-ajit.khaparde@broadcom.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148712
_Compilation OK_
Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Wed, 20 Nov 2024 09:00:58 -0800
DPDK git baseline: Repo:dpdk-next-net-brcm
Branch: for-next-net
CommitID: 0c0cd5ffb0f7fc085b54d91e15cc6d0f0fdf9921
148712 --> 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-20 17:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241120170058.18742-1-ajit.khaparde@broadcom.com>
2024-11-20 16:29 ` qemudev [this message]
2024-11-20 16:33 ` qemudev
2024-11-20 17:02 ` checkpatch
2024-11-20 18:05 ` 0-day Robot
2024-11-20 19:41 ` |PENDING| " dpdklab
2024-11-20 19:48 ` |SUCCESS| " dpdklab
2024-11-20 19:50 ` |PENDING| " dpdklab
2024-11-20 19:55 ` dpdklab
2024-11-20 19:55 ` |SUCCESS| " dpdklab
2024-11-20 19:58 ` dpdklab
2024-11-20 20:02 ` dpdklab
2024-11-20 20:33 ` dpdklab
2024-11-20 20:49 ` dpdklab
2024-11-20 20:53 ` dpdklab
2024-11-20 20:57 ` dpdklab
2024-11-20 20:58 ` dpdklab
2024-11-20 21:10 ` dpdklab
2024-11-20 21:19 ` dpdklab
2024-11-20 21:43 ` dpdklab
2024-11-20 21:47 ` dpdklab
2024-11-20 21:49 ` dpdklab
2024-11-20 21:55 ` dpdklab
2024-11-20 21:57 ` dpdklab
2024-11-20 21:59 ` dpdklab
2024-11-20 22:08 ` dpdklab
2024-11-20 22:18 ` dpdklab
2024-11-20 22:18 ` 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=202411201629.4AKGT9OG117704@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).