automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw159400 [PATCH v2] examples/ethtool: fix buffer size for pkt pool name
Date: Mon, 22 Dec 2025 17:01:33 +0800	[thread overview]
Message-ID: <202512220901.5BM91XbR3053614@localhost.localdomain> (raw)
In-Reply-To: <20251222083858.1035980-1-shperetz@nvidia.com>

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

_Compilation OK_

Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Mon, 22 Dec 2025 10:38:58 +0200
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: cd60dcd503b91956f966a1f6d595b35d256ac00f

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


  parent reply	other threads:[~2025-12-22  9:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251222083858.1035980-1-shperetz@nvidia.com>
2025-12-22  8:38 ` checkpatch
2025-12-22  9:01 ` qemudev [this message]
2025-12-22  9:06 ` qemudev
2025-12-22  9:23 ` 0-day Robot
2025-12-22  9:23 ` 0-day Robot
2026-01-09 11:09 ` |SUCCESS| pw159400 [PATCH] [v2] examples/ethtool: fix buffer size fo dpdklab
2026-01-09 11:46 ` dpdklab
2026-01-09 11:46 ` dpdklab
2026-01-09 11:47 ` dpdklab
2026-01-09 11:48 ` dpdklab
2026-01-09 11:48 ` dpdklab
2026-01-09 11:57 ` dpdklab
2026-01-09 12:05 ` dpdklab
2026-01-09 12:09 ` dpdklab
2026-01-09 12:13 ` dpdklab
2026-01-09 12:32 ` dpdklab
2026-01-09 12:33 ` dpdklab
2026-01-09 12:35 ` dpdklab
2026-01-09 12:36 ` dpdklab
2026-01-09 12:52 ` dpdklab
2026-01-09 12:54 ` dpdklab
2026-01-09 13:04 ` dpdklab
2026-01-09 13:07 ` dpdklab
2026-01-09 15:46 ` |PENDING| " dpdklab
2026-01-09 15:50 ` dpdklab
2026-01-09 16:54 ` |SUCCESS| " dpdklab
2026-01-09 17:19 ` dpdklab
2026-01-10  1:15 ` dpdklab
2026-01-10  2:02 ` dpdklab
2026-01-10  3:12 ` dpdklab
2026-01-10  3:23 ` dpdklab
2026-01-10  3:43 ` dpdklab
2026-01-10  3:51 ` dpdklab
2026-01-10 10:05 ` |PENDING| " dpdklab
2026-01-11  4:03 ` |SUCCESS| " dpdklab
2026-01-11  4:22 ` dpdklab
2026-01-11  4:46 ` dpdklab
2026-01-11  5:04 ` dpdklab
2026-01-11  9:40 ` dpdklab
2026-01-11 10:17 ` dpdklab
2026-01-12  8:17 ` 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=202512220901.5BM91XbR3053614@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).