From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw159607 [PATCH] maintainers: update for bnxt driver
Date: Thu, 08 Jan 2026 12:31:57 -0800 (PST) [thread overview]
Message-ID: <6960143d.050a0220.c5391.55b0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20260106150012.49022-1-ajit.khaparde@broadcom.com>
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/159607
_Testing PASS_
Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Tuesday, January 06 2026 15:00:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cd60dcd503b91956f966a1f6d595b35d256ac00f
159607 --> testing pass
Test environment and result as below:
+------------------------------+----------+
| Environment | abi_test |
+==============================+==========+
| CentOS Stream 9 | PASS |
+------------------------------+----------+
| Debian GNU/Linux 12 | PASS |
+------------------------------+----------+
| CentOS Stream 10 | PASS |
+------------------------------+----------+
| Fedora Linux 42 | PASS |
+------------------------------+----------+
| Red Hat Enterprise Linux 9.7 | PASS |
+------------------------------+----------+
| openSUSE Leap 15.6 | PASS |
+------------------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------------------+----------+
| Ubuntu 24.04 | PASS |
+------------------------------+----------+
CentOS Stream 9
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-14)
Debian GNU/Linux 12
Kernel: 5.15
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
CentOS Stream 10
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.3.1 20251022 (Red Hat 14.3.1-4)
Fedora Linux 42
Kernel: 5.15
Compiler: clang gcc (GCC) 15.2.1 20251111 (Red Hat 15.2.1-4)
Red Hat Enterprise Linux 9.7
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
openSUSE Leap 15.6
Kernel: 5.15
Compiler: gcc gcc (SUSE Linux) 7.5.0
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
Ubuntu 24.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34798/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2026-01-08 20:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260106150012.49022-1-ajit.khaparde@broadcom.com>
2026-01-06 15:01 ` checkpatch
2026-01-06 16:13 ` qemudev
2026-01-06 16:18 ` qemudev
2026-01-06 16:46 ` 0-day Robot
2026-01-06 16:46 ` 0-day Robot
2026-01-07 17:36 ` dpdklab
2026-01-07 17:42 ` dpdklab
2026-01-07 17:47 ` dpdklab
2026-01-07 17:56 ` dpdklab
2026-01-07 17:59 ` dpdklab
2026-01-07 18:08 ` dpdklab
2026-01-07 23:54 ` |PENDING| " dpdklab
2026-01-08 0:10 ` dpdklab
2026-01-08 0:58 ` |SUCCESS| " dpdklab
2026-01-08 1:00 ` dpdklab
2026-01-08 3:32 ` dpdklab
2026-01-08 20:27 ` dpdklab
2026-01-08 20:31 ` dpdklab [this message]
2026-01-08 21:35 ` dpdklab
2026-01-08 22:01 ` dpdklab
2026-01-08 22:17 ` |FAILURE| " dpdklab
2026-01-08 22:28 ` dpdklab
2026-01-08 22:57 ` |SUCCESS| " dpdklab
2026-01-08 23:01 ` dpdklab
2026-01-08 23:03 ` dpdklab
2026-01-08 23:33 ` dpdklab
2026-01-09 0:09 ` dpdklab
2026-01-09 22: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=6960143d.050a0220.c5391.55b0SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).