DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org
Cc: dev@dpdk.org, Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
	Ali Alnubani <alialnu@nvidia.com>,
	David Christensen <drc@linux.vnet.ibm.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Jerin Jacob <jerinj@marvell.com>,
	John McNamara <john.mcnamara@intel.com>,
	Ju-Hyoung Lee <juhlee@microsoft.com>,
	Luca Boccassi <bluca@debian.org>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Shani Peretz <shperetz@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: 25.11.3 patches review and test
Date: Wed, 5 Aug 2026 11:33:42 +0100	[thread overview]
Message-ID: <021dca67-9966-46e7-bdd3-c3dc838099d9@redhat.com> (raw)
In-Reply-To: <20260804104755.135019-1-ktraynor@redhat.com>

On 8/4/26 11:47, Kevin Traynor wrote:
> Hi all,
> 
> Here is a list of patches targeted for stable release 25.11.3.
> 
> The planned date for the final release is 20th August.
> 
> Please help with testing and validation of your use cases and report
> any issues/results with reply-all to this mail. For the final release
> the fixes and reported validations will be added to the release notes.
> 
> A release candidate tarball can be found at:
> 
>      https://dpdk.org/browse/dpdk-stable/tag/?id=v25.11.3-rc1
> 
> These patches are located at branch 25.11 of dpdk-stable repo:
>      https://dpdk.org/browse/dpdk-stable/
> 
> Thanks.
> 
> Kevin

Hi All. A few new backports [0] have come in since RC1 was sent. I will 
apply them and give the rest of the day in case there are any others. I 
will send out a new release candidate tomorrow AM.

So if anyone is about to begin testing RC1, it might be worth to 
hold-off for 24 hours.

thanks,
Kevin.

[0]
afa438ffc4 net/iavf: report selected burst mode when no-poll active
299a834154 net/mlx5: redirect LACP traffic for legacy E-Switch
a32d39d583 net/bnxt: fix Rx timestamping for non-PTP packets
07f9221521 net/bnxt: fix PTP timestamp flags in scalar Rx
94bf87ff04 net/bnxt: fix LRO capability reporting


  reply	other threads:[~2026-08-05 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 10:47 25.11.3 patches review and test Kevin Traynor
2026-08-05 10:33 ` Kevin Traynor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-06  9:38 Kevin Traynor

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=021dca67-9966-46e7-bdd3-c3dc838099d9@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=alialnu@nvidia.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=juhlee@microsoft.com \
    --cc=rasland@nvidia.com \
    --cc=shperetz@nvidia.com \
    --cc=stable@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