automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148552 [PATCH] net/i40e: fix read register return status check
Date: Sat, 16 Nov 2024 02:43:07 +0800	[thread overview]
Message-ID: <202411151843.4AFIh7mj1172019@localhost.localdomain> (raw)
In-Reply-To: <20241115191425.970929-1-vladimir.medvedkin@intel.com>

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

_Compilation OK_

Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Fri, 15 Nov 2024 19:14:25 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: c5df7a373ad07413d9652479272cd16adf989b06

148552 --> 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-11-15 19:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241115191425.970929-1-vladimir.medvedkin@intel.com>
2024-11-15 18:43 ` qemudev [this message]
2024-11-15 18:47 ` qemudev
2024-11-15 19:14 ` checkpatch
2024-11-15 20:04 ` 0-day Robot
2024-11-15 20:36 ` |PENDING| pw148552 [PATCH] net/i40e: fix read register return status dpdklab
2024-11-15 20:43 ` |SUCCESS| " dpdklab
2024-11-15 20:48 ` |PENDING| " dpdklab
2024-11-15 20:49 ` |SUCCESS| " dpdklab
2024-11-15 20:53 ` dpdklab
2024-11-15 20:57 ` dpdklab
2024-11-15 21:12 ` dpdklab
2024-11-15 21:13 ` dpdklab
2024-11-15 21:19 ` dpdklab
2024-11-15 21:19 ` dpdklab
2024-11-15 21:25 ` dpdklab
2024-11-15 21:28 ` |WARNING| " dpdklab
2024-11-15 21:42 ` |SUCCESS| " dpdklab
2024-11-15 22:00 ` dpdklab
2024-11-15 22:00 ` dpdklab
2024-11-16  1:26 ` 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=202411151843.4AFIh7mj1172019@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).