From: Kevin Traynor <ktraynor@redhat.com>
To: "Stokes, Ian" <ian.stokes@intel.com>,
"luca.boccassi@gmail.com" <luca.boccassi@gmail.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: 21.11.2 patches review and test
Date: Mon, 29 Aug 2022 17:20:06 +0100 [thread overview]
Message-ID: <6abddddd-cae2-1fd4-e945-7141c23fcbda@redhat.com> (raw)
In-Reply-To: <CY5PR11MB6464CE054649391073B32D1A92769@CY5PR11MB6464.namprd11.prod.outlook.com>
On 29/08/2022 14:00, Stokes, Ian 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
>
> Hi Luca,
>
> 21.11.2 validated by Intel for i40e, ICE, vhost and MTU for OVS with DPDK. No issues encountered.
>
> Tanks
> Ian
Thanks Ian. Added this to the validation notes.
Kevin.
prev parent reply other threads:[~2022-08-29 16:20 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
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 [this message]
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=6abddddd-cae2-1fd4-e945-7141c23fcbda@redhat.com \
--to=ktraynor@redhat.com \
--cc=ian.stokes@intel.com \
--cc=luca.boccassi@gmail.com \
--cc=stable@dpdk.org \
/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).