patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Luca Boccassi <bluca@debian.org>, "stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	John McNamara <john.mcnamara@intel.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: RE: 22.11.6 patches review and test
Date: Thu, 15 Aug 2024 16:19:28 +0000	[thread overview]
Message-ID: <PH7PR12MB91733712B021EDFE12AD05E2DA802@PH7PR12MB9173.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAMw=ZnSJkD4zM63qf6a6uMcjtxzweKUkOyVP+24XFNHY0v9pkA@mail.gmail.com>

> -----Original Message-----
> From: Luca Boccassi <bluca@debian.org>
> Sent: Thursday, August 15, 2024 2:11 PM
> To: stable@dpdk.org
> Cc: dev@dpdk.org; Ali Alnubani <alialnu@nvidia.com>; John McNamara
> <john.mcnamara@intel.com>; Raslan Darawsheh <rasland@nvidia.com>; NBU-
> Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>
> Subject: Re: 22.11.6 patches review and test
> 
> 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!

Hi Luca,

We will report our results hopefully by Monday. Apologies for the delay.

Thanks,
Ali

  reply	other threads:[~2024-08-15 16:19 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
2024-08-15 16:19   ` Ali Alnubani [this message]
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=PH7PR12MB91733712B021EDFE12AD05E2DA802@PH7PR12MB9173.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.com \
    --cc=bluca@debian.org \
    --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).