DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Ali Alnubani <alialnu@nvidia.com>, Raslan Darawsheh <rasland@nvidia.com>
Cc: dev@dpdk.org, John McNamara <john.mcnamara@intel.com>,
	 Thomas Monjalon <thomas@monjalon.net>,
	stable@dpdk.org
Subject: Re: 22.11.8 patches review and test
Date: Tue, 8 Apr 2025 14:45:26 +0100	[thread overview]
Message-ID: <CAMw=ZnTOVHyvNxGbcFWRt2Xw0YqRXnKC9VjzVOsEn=utu+mrCw@mail.gmail.com> (raw)
In-Reply-To: <20250326115132.1444530-1-luca.boccassi@gmail.com>

On Wed, 26 Mar 2025 at 11:51, <luca.boccassi@gmail.com> wrote:
>
> Hi all,
>
> Here is a list of patches targeted for stable release 22.11.8.
>
> The planned date for the final release is 2025/04/10.
>
> 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=v22.11.8-rc1
>
> These patches are located at branch 22.11 of dpdk-stable repo:
>     https://dpdk.org/browse/dpdk-stable/

Hi Ali and Raslan,

Will the NVIDIA validation team have bandwidth to run the tests for
22.11 for this round? Thanks!

  parent reply	other threads:[~2025-04-08 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 11:51 luca.boccassi
2025-03-31  9:08 ` Yanghang Liu
2025-03-31 10:08   ` Luca Boccassi
2025-04-03  9:40 ` Xu, HailinX
2025-04-03  9:47   ` Luca Boccassi
2025-04-08 13:45 ` Luca Boccassi [this message]
2025-04-08 18:31 ` Ali Alnubani
2025-04-08 18:39   ` Luca Boccassi

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='CAMw=ZnTOVHyvNxGbcFWRt2Xw0YqRXnKC9VjzVOsEn=utu+mrCw@mail.gmail.com' \
    --to=bluca@debian.org \
    --cc=alialnu@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=rasland@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;
as well as URLs for NNTP newsgroup(s).