automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw155446 [PATCH] lib/ethdev: fix segfault in secondary process by validating dev_private pointer
Date: Wed, 23 Jul 2025 11:55:56 +0800	[thread overview]
Message-ID: <202507230355.56N3tuPA1547803@localhost.localdomain> (raw)
In-Reply-To: <20250723042959.1576338-1-14pwcse1224@uetpeshawar.edu.pk>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/155446

_Compilation OK_

Submitter: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
Date: Wed, 23 Jul 2025 00:29:59 -0400
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: b78afde1fed9e11ee5cdce333a1a69dd7a9cf13e

155446 --> 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


       reply	other threads:[~2025-07-23  4:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250723042959.1576338-1-14pwcse1224@uetpeshawar.edu.pk>
2025-07-23  3:55 ` qemudev [this message]
2025-07-23  4:03 ` |FAILURE| " qemudev
2025-07-23  4:29 ` |WARNING| " checkpatch
2025-07-23  5:43 ` |SUCCESS| pw155446 [PATCH] lib/ethdev: fix segfault in secondary pro dpdklab
2025-07-23  5:47 ` |PENDING| " dpdklab
2025-07-23  5:50 ` |SUCCESS| " dpdklab
2025-07-23  5:51 ` |SUCCESS| pw155446 [PATCH] lib/ethdev: fix segfault in secondary process by validating dev_private pointer 0-day Robot
2025-07-23  6:00 ` |SUCCESS| pw155446 [PATCH] lib/ethdev: fix segfault in secondary pro dpdklab
2025-07-23  6:08 ` dpdklab
2025-07-23  6:10 ` dpdklab
2025-07-23  6:28 ` dpdklab
2025-07-23  6:37 ` dpdklab
2025-07-23  6:57 ` |PENDING| " dpdklab
2025-07-23  7:05 ` dpdklab
2025-07-23  8:04 ` |SUCCESS| " dpdklab
2025-07-23  8:27 ` dpdklab
2025-07-23  9:25 ` dpdklab
2025-07-23  9:57 ` |PENDING| " dpdklab
2025-07-23 10:18 ` |SUCCESS| " dpdklab
2025-07-23 10:57 ` dpdklab
2025-07-23 10:57 ` dpdklab
2025-07-23 10:59 ` dpdklab
2025-07-23 10:59 ` dpdklab
2025-07-23 10:59 ` dpdklab
2025-07-23 10:59 ` dpdklab
2025-07-23 14:44 ` dpdklab
2025-07-23 17:48 ` dpdklab
2025-07-23 17:48 ` dpdklab
2025-07-23 21:29 ` 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=202507230355.56N3tuPA1547803@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).