patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: stable@dpdk.org
Cc: dev@dpdk.org, Ali Alnubani <alialnu@nvidia.com>,
	 John McNamara <john.mcnamara@intel.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: 22.11.6 patches review and test
Date: Thu, 15 Aug 2024 12:10:48 +0100	[thread overview]
Message-ID: <CAMw=ZnSJkD4zM63qf6a6uMcjtxzweKUkOyVP+24XFNHY0v9pkA@mail.gmail.com> (raw)
In-Reply-To: <20240731193710.3069297-1-luca.boccassi@gmail.com>

On Wed, 31 Jul 2024 at 20:37, <luca.boccassi@gmail.com> wrote:
>
> Hi all,
>
> Here is a list of patches targeted for stable release 22.11.6.
>
> The planned date for the final release is August 20th.
>
> 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.6-rc1
>
> These patches are located at branch 22.11 of dpdk-stable repo:
>     https://dpdk.org/browse/dpdk-stable/
>
> Thanks.
>
> Luca Boccassi

Hi Ali,

As the deadline is approaching, I wanted to double check whether
NVIDIA is planning to run regression tests for 22.11.6? If you need
more time it's fine to extend the deadline, but if you do not have the
bandwidth for this cycle that's ok too, just let me know and I'll go
ahead with the release without waiting. Thanks!

  parent reply	other threads:[~2024-08-15 11:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 19:37 luca.boccassi
2024-08-01 11:59 ` Luca Boccassi
2024-08-05  5:45 ` YangHang Liu
2024-08-05 12:27   ` Luca Boccassi
2024-08-09 10:19 ` Xu, HailinX
2024-08-09 10:26   ` Luca Boccassi
2024-08-15 11:10 ` Luca Boccassi [this message]
2024-08-15 16:19   ` Ali Alnubani
2024-08-15 16:21     ` Luca Boccassi
2024-08-20  7:21 ` Ali Alnubani
2024-08-20  8:58   ` 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=ZnSJkD4zM63qf6a6uMcjtxzweKUkOyVP+24XFNHY0v9pkA@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).