patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@mellanox.com>
To: Kevin Traynor <ktraynor@redhat.com>, dpdk stable <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] 18.11.1 patches review and test
Date: Wed, 27 Mar 2019 14:41:33 +0000	[thread overview]
Message-ID: <AM6PR05MB4405234D5196649B2087F50AD7580@AM6PR05MB4405.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20190322151023.6616-1-ktraynor@redhat.com>

Hi

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Kevin Traynor
> Sent: Friday, March 22, 2019 5:10 PM
> To: dpdk stable <stable@dpdk.org>
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] 18.11.1 patches review and test
> 
> Hi all,
> 
> Here is a list of patches targeted for LTS release 18.11.1. Please help review
> and test. The planned date for the final release is April 8th. Before that,
> please shout if anyone has objections with these patches being applied.
> 
> Also for the companies committed to running regression tests, please run
> the tests and report any issue before the release date.
> 
> To avoid further delays, in the absence of any reported release blockers the
> release will go ahead on April 8th. I will add some release notes regarding list
> of bugfixes and areas validated.
> 

I ran our tests and didn't see any issues. Testing matrix can be found here:
http://mails.dpdk.org/archives/stable/2019-March/013619.html

Thanks,
Ali

  reply	other threads:[~2019-03-27 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 15:10 [dpdk-stable] " Kevin Traynor
2019-03-27 14:41 ` Ali Alnubani [this message]
2019-03-27 16:43   ` [dpdk-stable] [dpdk-dev] " Kevin Traynor
2019-04-03  9:16 ` Ian Stokes
2019-04-03 14:29   ` 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=AM6PR05MB4405234D5196649B2087F50AD7580@AM6PR05MB4405.eurprd05.prod.outlook.com \
    --to=alialnu@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=ktraynor@redhat.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).