automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw154633-154634 [PATCH v2 2/2] common/cnxk: fix null pointer checks
Date: Mon, 23 Jun 2025 12:15:19 +0800	[thread overview]
Message-ID: <202506230415.55N4FJSL991162@localhost.localdomain> (raw)
In-Reply-To: <20250623044907.2906896-2-rbhansali@marvell.com>

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

_Compilation OK_

Submitter: Rahul Bhansali <rbhansali@marvell.com>
Date: Mon, 23 Jun 2025 10:19:06 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
  Branch: for-next-net
  CommitID: 794cce6797bbec2bd290573cfafe71a5a41ea9d5

154633-154634 --> 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-06-23  4:51 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250623044907.2906896-2-rbhansali@marvell.com>
2025-06-23  4:15 ` qemudev [this message]
2025-06-23  4:19 ` qemudev
2025-06-23  4:49 ` |SUCCESS| pw154634 " checkpatch
2025-06-23  5:44 ` 0-day Robot
2025-06-23  6:18 ` |SUCCESS| pw154633-154634 [PATCH] [v2,2/2] common/cnxk: fix null poi dpdklab
2025-06-23  6:29 ` |PENDING| " dpdklab
2025-06-23  6:33 ` |SUCCESS| " dpdklab
2025-06-23  6:53 ` dpdklab
2025-06-23  6:59 ` |FAILURE| " dpdklab
2025-06-23  7:00 ` dpdklab
2025-06-23  7:03 ` |PENDING| " dpdklab
2025-06-23  7:10 ` |FAILURE| " dpdklab
2025-06-23  7:15 ` |SUCCESS| " dpdklab
2025-06-23  7:17 ` |FAILURE| " dpdklab
2025-06-23  7:24 ` |SUCCESS| " dpdklab
2025-06-23  7:31 ` dpdklab
2025-06-23  8:30 ` dpdklab
2025-06-23  8:36 ` |FAILURE| " dpdklab
2025-06-23  8:47 ` |PENDING| " dpdklab
2025-06-23  9:18 ` |FAILURE| " dpdklab
2025-06-23  9:57 ` |SUCCESS| " dpdklab
2025-06-23 10:18 ` dpdklab
2025-06-23 10:37 ` dpdklab
2025-06-23 13:14 ` |PENDING| " dpdklab
2025-06-23 13:15 ` |SUCCESS| " dpdklab
2025-06-23 13:25 ` |PENDING| " dpdklab
2025-06-23 13:30 ` dpdklab
2025-06-23 13:30 ` |SUCCESS| " dpdklab
2025-06-23 13:46 ` dpdklab
2025-06-23 13:51 ` |PENDING| " dpdklab
2025-06-23 13:53 ` |SUCCESS| " dpdklab
2025-06-23 14:04 ` |PENDING| " dpdklab
2025-06-23 14:17 ` |SUCCESS| " dpdklab
2025-06-23 14:24 ` dpdklab
2025-06-23 14:32 ` dpdklab
2025-06-23 15:29 ` dpdklab
2025-06-23 15:35 ` |WARNING| " 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=202506230415.55N4FJSL991162@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).