DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thinh Tran <thinhtr@linux.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>
Cc: rileyf@linux.ibm.com
Subject: Re: DPDK release candidate 25.07-rc3
Date: Tue, 15 Jul 2025 09:15:19 -0500	[thread overview]
Message-ID: <086c9e27-466a-43b1-86e7-8dc4095512d0@linux.ibm.com> (raw)
In-Reply-To: <9991491.lyo4hBLbkK@thomas>

IBM - Power Systems Testing
DPDK v25.07-rc3


* Build CI on Fedora 40, 41 and 42 container images for ppc64le
* Basic PF on Mellanox: No issue found
* Performance: not tested.
* OS:- RHEL 9.4  kernel: 5.14.0-427.40.1.el9_4.ppc64le
              with gcc version  11.4.1 20231218 (Red Hat 11.4.1-3)
	 - SLES 15 SP6 6.4.0-150600.21-default
  	     with gcc version 13.2.1 20240206 (SUSE Linux)

Systems tested:
  - LPARs on IBM Power10 CHRP IBM,9105-22A
     NICs:
     -  Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
     - firmware version: 16.35.2000
     - OFED 25.04-0.6.1

Regards,
Thinh Tran

On 7/9/2025 4:26 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v25.07-rc3
> 
> There are 86 new patches in this snapshot.
> 
> Release notes:
> 	https://doc.dpdk.org/guides/rel_notes/release_25_07.html
> 
> Please test and report new issues on https://bugs.dpdk.org
> 
> Only documentation changes are expected at this stage.
> 
> If no major blocker is discovered,
> this release cycle may be closed during the next week.
> 
> Thank you everyone
> 
> 


      parent reply	other threads:[~2025-07-15 14:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 21:26 Thomas Monjalon
2025-07-13 14:52 ` Ali Alnubani
2025-07-15 14:15 ` 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=086c9e27-466a-43b1-86e7-8dc4095512d0@linux.ibm.com \
    --to=thinhtr@linux.ibm.com \
    --cc=dev@dpdk.org \
    --cc=rileyf@linux.ibm.com \
    --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).