patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org, John McNamara <john.mcnamara@intel.com>,
	yuan.peng@intel.com, zhaoyan.chen@intel.com, "Xu,
	HailinX" <hailinx.xu@intel.com>
Cc: dev@dpdk.org, benjamin.walker@intel.com,
	Ian Stokes <ian.stokes@intel.com>,
	Luca Boccassi <bluca@debian.org>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: 21.11.5 patches review and test
Date: Mon, 21 Aug 2023 10:01:46 +0100	[thread overview]
Message-ID: <f72dcc97-fad4-e93f-5073-bcf75da5b64e@redhat.com> (raw)
In-Reply-To: <20230802163117.372039-1-ktraynor@redhat.com>

On 02/08/2023 17:31, Kevin Traynor wrote:
> Hi all,
> 
> Here is a list of patches targeted for stable release 21.11.5.
> 
> The planned date for the final release is 22nd August.
> 
> 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.5-rc1
> 
> These patches are located at branch 21.11 of dpdk-stable repo:
>      https://dpdk.org/browse/dpdk-stable/
> 
> Thanks.
> 
> Kevin
> 

Hi,

Any updates from Intel validation team ? The release is due tomorrow 
(22nd) but I can postpone it if you need a few more days to complete 
testing.

thanks,
Kevin.


  parent reply	other threads:[~2023-08-21  9:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 16:31 Kevin Traynor
2023-08-15  9:50 ` YangHang Liu
2023-08-21  8:56   ` Kevin Traynor
2023-08-17  9:45 ` Ali Alnubani
2023-08-21  8:58   ` Kevin Traynor
2023-08-21  9:01 ` Kevin Traynor [this message]
2023-08-21 10:50   ` Mcnamara, John
2023-08-21 12:37     ` Kevin Traynor
2023-08-23  9:55       ` Mcnamara, John
2023-08-23 10:04         ` Kevin Traynor
2023-08-24  6:07 ` Xu, HailinX
2023-08-24 10:59   ` 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=f72dcc97-fad4-e93f-5073-bcf75da5b64e@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=benjamin.walker@intel.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=hailinx.xu@intel.com \
    --cc=ian.stokes@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --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).