automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138436-138437 [PATCH 2/2] net/bnxt: fix init failures
Date: Sat, 16 Mar 2024 11:49:15 +0800	[thread overview]
Message-ID: <202403160349.42G3nFbp2023349@localhost.localdomain> (raw)
In-Reply-To: <20240316035441.76438-3-ajit.khaparde@broadcom.com>

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

_Compilation OK_

Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Fri, 15 Mar 2024 20:54:40 -0700
DPDK git baseline: Repo:dpdk-next-net-brcm
  Branch: for-next-net
  CommitID: 7f82e9c89f3514715533feb34f46ff1ea95c6f98

138436-138437 --> 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:[~2024-03-16  4:14 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240316035441.76438-3-ajit.khaparde@broadcom.com>
2024-03-16  3:49 ` qemudev [this message]
2024-03-16  3:53 ` qemudev
2024-03-16  4:12 ` |SUCCESS| pw138437 " checkpatch
2024-03-16  5:03 ` 0-day Robot
2024-03-16  5:36 ` |SUCCESS| pw138436-138437 [PATCH] [2/2] " dpdklab
2024-03-16  5:36 ` dpdklab
2024-03-16  5:37 ` dpdklab
2024-03-16  5:38 ` dpdklab
2024-03-16  5:41 ` dpdklab
2024-03-16  5:41 ` dpdklab
2024-03-16  5:42 ` dpdklab
2024-03-16  5:43 ` dpdklab
2024-03-16  5:44 ` dpdklab
2024-03-16  5:45 ` dpdklab
2024-03-16  5:45 ` dpdklab
2024-03-16  5:46 ` dpdklab
2024-03-16  5:47 ` dpdklab
2024-03-16  5:47 ` dpdklab
2024-03-16  5:51 ` dpdklab
2024-03-16  5:52 ` dpdklab
2024-03-16  5:55 ` dpdklab
2024-03-16  5:56 ` dpdklab
2024-03-16  5:57 ` dpdklab
2024-03-16  5:58 ` dpdklab
2024-03-16  5:59 ` dpdklab
2024-03-16  5:59 ` dpdklab
2024-03-16  6:00 ` dpdklab
2024-03-16  6:00 ` dpdklab
2024-03-16  6:01 ` dpdklab
2024-03-16  6:02 ` dpdklab
2024-03-16  6:02 ` dpdklab
2024-03-16  6:03 ` dpdklab
2024-03-16  6:03 ` dpdklab
2024-03-16  6:03 ` dpdklab
2024-03-16  6:04 ` dpdklab
2024-03-16  6:04 ` dpdklab
2024-03-16  6:04 ` dpdklab
2024-03-16  6:04 ` dpdklab
2024-03-16  6:10 ` dpdklab
2024-03-16  6:11 ` dpdklab
2024-03-16  6:14 ` dpdklab
2024-03-16  6:14 ` dpdklab
2024-03-16  6:15 ` dpdklab
2024-03-16  6:16 ` dpdklab
2024-03-16  6:16 ` dpdklab
2024-03-16  6:16 ` dpdklab
2024-03-16  6:16 ` dpdklab
2024-03-16  6:17 ` dpdklab
2024-03-16  6:17 ` dpdklab
2024-03-16  6:17 ` dpdklab
2024-03-16  6:24 ` dpdklab
2024-03-16  6:24 ` dpdklab
2024-03-16  6:25 ` dpdklab
2024-03-16  6:25 ` dpdklab
2024-03-16  6:26 ` dpdklab
2024-03-16  6:26 ` dpdklab
2024-03-16  6:28 ` dpdklab
2024-03-16  6:30 ` dpdklab
2024-03-16  6:30 ` dpdklab
2024-03-16  6:32 ` dpdklab
2024-03-16  6:41 ` dpdklab
2024-03-16  6:41 ` dpdklab
2024-03-16  6:46 ` dpdklab
2024-03-16  6:58 ` dpdklab
2024-03-16  7:07 ` dpdklab
2024-03-16  7:08 ` dpdklab
2024-03-16  7:08 ` dpdklab
2024-03-16  7:09 ` dpdklab
2024-03-16  7:12 ` dpdklab
2024-03-16  7:14 ` dpdklab
2024-03-16  7:14 ` dpdklab
2024-03-16  7:14 ` dpdklab
2024-03-16  7:14 ` dpdklab
2024-03-16  7:15 ` dpdklab
2024-03-16  7:15 ` dpdklab
2024-03-16  7:19 ` dpdklab
2024-03-16  7:27 ` dpdklab
2024-03-19 16:06 ` dpdklab
2024-03-19 16:55 ` 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=202403160349.42G3nFbp2023349@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).