patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: stable@dpdk.org
Cc: dev@dpdk.org, Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
	Ali Alnubani <alialnu@nvidia.com>,
	benjamin.walker@intel.com,
	David Christensen <drc@linux.vnet.ibm.com>,
	 Hemant Agrawal <hemant.agrawal@nxp.com>,
	Ian Stokes <ian.stokes@intel.com>,
	Jerin Jacob <jerinj@marvell.com>,
	 John McNamara <john.mcnamara@intel.com>,
	Ju-Hyoung Lee <juhlee@microsoft.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Pei Zhang <pezhang@redhat.com>,
	qian.q.xu@intel.com,  Raslan Darawsheh <rasland@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	yuan.peng@intel.com,  zhaoyan.chen@intel.com,
	yanghliu@redhat.com
Subject: Re: 21.11.2 patches review and test
Date: Thu, 28 Jul 2022 13:34:16 +0100	[thread overview]
Message-ID: <6f814f47ae0b26c32dbd6227ab9f6d90a9544fd7.camel@debian.org> (raw)
In-Reply-To: <20220718095859.613018-1-luca.boccassi@gmail.com>

On Mon, 2022-07-18 at 10:58 +0100, luca.boccassi@gmail.com wrote:
> Hi all,
> 
> Here is a list of patches targeted for stable release 21.11.2.
> 
> The planned date for the final release is August 29th.
> 
> 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=v21.11.2-rc1
> 
> These patches are located at branch 21.11 of dpdk-stable repo:
>     https://dpdk.org/browse/dpdk-stable/
> 
> Thanks.
> 
> Luca Boccassi

Hello,

Any update from any of the validation teams? Any indication on how the
tests are going?

-- 
Kind regards,
Luca Boccassi

  parent reply	other threads:[~2022-07-28 12:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  9:58 luca.boccassi
2022-07-19  2:40 ` Pei Zhang
2022-07-28 12:34 ` Luca Boccassi [this message]
2022-07-28 12:48   ` Ali Alnubani
2022-08-16  7:33     ` Ali Alnubani
2022-08-16 10:05       ` Luca Boccassi
2022-07-29  3:00   ` Jiang, YuX
2022-07-29 11:26     ` Jiang, YuX
2022-08-02 10:00       ` Luca Boccassi
2022-08-02 10:14         ` Jiang, YuX
2022-08-04  7:28           ` Jiang, YuX
2022-08-16 11:39             ` Luca Boccassi
2022-08-17 10:00               ` Jiang, YuX
2022-08-26  8:13                 ` Jiang, YuX
2022-08-26  9:06                   ` Kevin Traynor
2022-08-02  3:29   ` YangHang Liu
2022-08-02  9:32     ` Luca Boccassi
2022-08-29 13:00 ` Stokes, Ian
2022-08-29 16:20   ` 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=6f814f47ae0b26c32dbd6227ab9f6d90a9544fd7.camel@debian.org \
    --to=bluca@debian.org \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=alialnu@nvidia.com \
    --cc=benjamin.walker@intel.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=ian.stokes@intel.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=juhlee@microsoft.com \
    --cc=ktraynor@redhat.com \
    --cc=pezhang@redhat.com \
    --cc=qian.q.xu@intel.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=yanghliu@redhat.com \
    --cc=yuan.peng@intel.com \
    --cc=zhaoyan.chen@intel.com \
    /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).