From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org, John McNamara <john.mcnamara@intel.com>
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>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
qian.q.xu@intel.com, Raslan Darawsheh <rasland@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>,
yanghliu@redhat.com, yuan.peng@intel.com, zhaoyan.chen@intel.com
Subject: Re: 21.11.6 patches review and test
Date: Tue, 9 Jan 2024 09:48:48 +0000 [thread overview]
Message-ID: <7f5e2cd0-c4a1-4fbf-b889-509bc664137b@redhat.com> (raw)
In-Reply-To: <20231220132243.126051-1-ktraynor@redhat.com>
On 20/12/2023 13:22, Kevin Traynor wrote:
> Hi all,
>
> Here is a list of patches targeted for stable release 21.11.6.
>
> The planned date for the final release is 12 January.
>
I have validation reports for Red Hat and Nvidia. Thank you.
Is there any validation results from Intel, or an ETA ?
> 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.6-rc1
>
> These patches are located at branch 21.11 of dpdk-stable repo:
> https://dpdk.org/browse/dpdk-stable/
>
> Thanks.
>
> Kevin
>
next prev parent reply other threads:[~2024-01-09 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 13:22 Kevin Traynor
2023-12-28 3:06 ` YangHang Liu
2024-01-03 14:43 ` Ali Alnubani
2024-01-09 9:41 ` Kevin Traynor
2024-01-09 9:48 ` Kevin Traynor [this message]
2024-01-10 1:28 ` Xu, HailinX
2024-01-10 9:46 ` Kevin Traynor
2024-01-15 7:50 ` Xu, HailinX
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=7f5e2cd0-c4a1-4fbf-b889-509bc664137b@redhat.com \
--to=ktraynor@redhat.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--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=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).