From: Thinh Tran <thinhtr@linux.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>
Subject: Re: release candidate 25.03-rc2
Date: Fri, 14 Mar 2025 14:26:16 -0500 [thread overview]
Message-ID: <9ecc5c6d-9472-41c9-884f-3d352fc93c49@linux.ibm.com> (raw)
In-Reply-To: <4098448.yKrmzQ4Hd0@thomas>
IBM - Power Systems Testing
DPDK v25.03-rc2
* Build CI on Fedora 39,40 and 41 container images for ppc64le
* Basic PF on Mellanox: No issue found
* Performance: not tested.
* OS:- RHEL 9.4 kernel: 5.14.0-427.13.1.el9_4.ppc64le
with gcc version 11.4.1 20231218 (Red Hat 11.4.1-3)
- RHEL 9.2 kernel: 5.14.0-284.52.1.el9_2.ppc64le
with gcc version 11.3.1 20221121 (Red Hat 11.3.1-4) (GCC)
- SLES 15-SP5 ppc64le kernel: 5.14.21-150500.55.44-default
with gcc version 12.3.0 (SUSE Linux)
Systems tested:
- LPARs on IBM Power10 CHRP IBM,9105-22A
NICs:
- Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
- firmware version: 16.35.4030
- OFED 25.01-0.6.0
Regards,
Thinh Tran
On 3/6/2025 11:42 AM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v25.03-rc2
>
> There are 251 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_25_03.html
>
> Most significant changes are in multiple drivers.
>
> Please test and report new issues on https://bugs.dpdk.org
>
> DPDK 25.03-rc3 is expected in one week.
> As it is a small release, we may try to close this cycle in advance.
>
> Thank you everyone
>
>
prev parent reply other threads:[~2025-03-14 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 17:42 Thomas Monjalon
2025-03-14 19:26 ` Thinh Tran [this message]
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=9ecc5c6d-9472-41c9-884f-3d352fc93c49@linux.ibm.com \
--to=thinhtr@linux.ibm.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).