From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw155372 [PATCH] net/ice: fix segfault in secondary process by validating dev_private pointer
Date: Mon, 21 Jul 2025 18:21:22 +0800 [thread overview]
Message-ID: <202507211021.56LALMIX568932@localhost.localdomain> (raw)
In-Reply-To: <20250721105522.1019515-1-14pwcse1224@uetpeshawar.edu.pk>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/155372
_Compilation OK_
Submitter: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
Date: Mon, 21 Jul 2025 06:55:22 -0400
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: a6b10031d251fcc7dadede461f7e1d005024b139
155372 --> 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:[~2025-07-21 10:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250721105522.1019515-1-14pwcse1224@uetpeshawar.edu.pk>
2025-07-21 10:21 ` qemudev [this message]
2025-07-21 10:26 ` qemudev
2025-07-21 10:54 ` |WARNING| " checkpatch
2025-07-21 11:43 ` |SUCCESS| " 0-day Robot
2025-07-21 11:43 ` |SUCCESS| pw155372 [PATCH] net/ice: fix segfault in secondary proces dpdklab
2025-07-21 11:47 ` dpdklab
2025-07-21 11:52 ` |PENDING| " dpdklab
2025-07-21 11:56 ` |SUCCESS| " dpdklab
2025-07-21 11:57 ` dpdklab
2025-07-21 12:01 ` |PENDING| " dpdklab
2025-07-21 12:06 ` |SUCCESS| " dpdklab
2025-07-21 12:08 ` dpdklab
2025-07-21 12:16 ` |PENDING| " dpdklab
2025-07-21 13:30 ` |SUCCESS| " dpdklab
2025-07-21 14:43 ` dpdklab
2025-07-21 14:48 ` |PENDING| " dpdklab
2025-07-21 16:00 ` |SUCCESS| " dpdklab
2025-07-21 16:00 ` dpdklab
2025-07-21 18:34 ` 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=202507211021.56LALMIX568932@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).