DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org
Cc: dev@dpdk.org, Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	Ali Alnubani <alialnu@mellanox.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>,
	Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
	pingx.yu@intel.com, qian.q.xu@intel.com,
	Raslan Darawsheh <rasland@mellanox.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	yuan.peng@intel.com, zhaoyan.chen@intel.com,
	hariprasad.govindharajan@intel.com
Subject: Re: [dpdk-dev] 18.11.11 (LTS) patches review and test
Date: Tue, 12 Jan 2021 09:45:48 +0000	[thread overview]
Message-ID: <70f9a178-6e9a-5e12-7b39-180264b670f6@redhat.com> (raw)
In-Reply-To: <20201217120304.351927-1-ktraynor@redhat.com>

Hi,

On 17/12/2020 12:03, Kevin Traynor wrote:
> Hi all,
> 
> Here is a list of patches targeted for LTS release 18.11.11.
> 
> The planned date for the final release is 19th January.
> 

The release is planned on the 19th. Please let me know about any other
validation testing. Reminder that this is the final planned 18.11 LTS
release.

thanks,
Kevin.

> Note, this is the last planned release of 18.11 LTS, and it will be
> unmaintained after this release, so I encourage anyone who is using
> 18.11 LTS to test.
> 
> 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=v18.11.11-rc1
> 
> These patches are located at branch 18.11 of dpdk-stable repo:
>     https://dpdk.org/browse/dpdk-stable/
> 
> Thanks.
> 
> Kevin.


  parent reply	other threads:[~2021-01-12  9:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 12:03 Kevin Traynor
2020-12-23  9:41 ` Pei Zhang
2021-01-05 16:24   ` Kevin Traynor
2020-12-29  9:01 ` Chen, BoX C
2021-01-05 16:23   ` Kevin Traynor
2021-01-06  2:08     ` Chen, BoX C
2021-01-12  9:45 ` Kevin Traynor [this message]
2021-01-14 14:32 ` Govindharajan, Hariprasad
2021-01-14 16:50   ` Kevin Traynor
2021-01-14 15:11 ` [dpdk-dev] [dpdk-stable] " Ali Alnubani
2021-01-14 16:55   ` Kevin Traynor
2021-01-20 10:55     ` Ali Alnubani

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=70f9a178-6e9a-5e12-7b39-180264b670f6@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=akhil.goyal@nxp.com \
    --cc=alialnu@mellanox.com \
    --cc=benjamin.walker@intel.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=hariprasad.govindharajan@intel.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=pingx.yu@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=rasland@mellanox.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).