From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Kevin Traynor <ktraynor@redhat.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>, Sitong Liu <siliu@redhat.com>,
Pei Zhang <pezhang@redhat.com>,
Raslan Darawsheh <rasland@mellanox.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Ian Stokes <ian.stokes@intel.com>,
Ali Alnubani <alialnu@mellanox.com>,
David Christensen <drc@linux.vnet.ibm.com>,
John McNamara <john.mcnamara@intel.com>,
Luca Boccassi <bluca@debian.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Akhil Goyal <akhil.goyal@nxp.com>
Subject: Re: [dpdk-stable] [dpdk-dev] DPDK 18.11.2 LTS update
Date: Thu, 16 May 2019 16:23:56 -0700 [thread overview]
Message-ID: <20190516162356.0488b379@hermes.lan> (raw)
In-Reply-To: <1728036.q3OyDDJpUi@xps>
On Thu, 16 May 2019 23:12:45 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> 16/05/2019 20:57, Kevin Traynor:
> > Plan is to have a 18.11.2 RC1 ready early next week for validation
> > teams. There are a small few outstanding backports that need authors
> > help - please send by next Monday so I can put into RC1.
>
> Please could you share the list of patches which need some help?
> Some fixes from 19.02 are still pending for help, right?
>
>
Will it include the necessary bits to support multi-process on Azure
(Failsafe, MLX, TAP)?
next prev parent reply other threads:[~2019-05-16 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 18:57 [dpdk-stable] " Kevin Traynor
2019-05-16 21:12 ` Thomas Monjalon
2019-05-16 23:23 ` Stephen Hemminger [this message]
2019-05-17 7:53 ` [dpdk-stable] [dpdk-dev] " Kevin Traynor
2019-05-17 7:41 ` [dpdk-stable] " 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=20190516162356.0488b379@hermes.lan \
--to=stephen@networkplumber.org \
--cc=akhil.goyal@nxp.com \
--cc=alialnu@mellanox.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=ktraynor@redhat.com \
--cc=pezhang@redhat.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@mellanox.com \
--cc=siliu@redhat.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).