DPDK patches and discussions
 help / color / mirror / Atom feed
From: Marco Varlese <mvarlese@suse.de>
To: Luca Boccassi <bluca@debian.org>, dpdk stable <stable@dpdk.org>
Cc: dev@dpdk.org, radu.nicolau@intel.com, qi.z.zhang@intel.com
Subject: Re: [dpdk-dev] 16.11.8 (LTS) patches review and test
Date: Wed, 29 Aug 2018 15:28:36 +0200	[thread overview]
Message-ID: <af9d1825a4e204669931366fb87344b9e2f6bb20.camel@suse.de> (raw)
In-Reply-To: <1535536543.1113.31.camel@debian.org>

Hi Luca & all,

I confirm tests carried out via test_pmd and Ovs-DPDK do not show any regression
for us.


Cheers,
Marco

On Wed, 2018-08-29 at 10:55 +0100, Luca Boccassi wrote:
> On Mon, 2018-08-27 at 17:17 +0100, Luca Boccassi wrote:
> > On Thu, 2018-08-23 at 09:55 +0100, Luca Boccassi wrote:
> > > On Mon, 2018-08-13 at 19:21 +0100, luca.boccassi@gmail.com wrote:
> > > > Hi all,
> > > > 
> > > > Here is a list of patches targeted for LTS release 16.11.8.
> > > > Please
> > > > help review and test. The planned date for the final release is
> > > > August
> > > > the 23rd.
> > > > 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.
> > > > 
> > > > A release candidate tarball can be found at:
> > > > 
> > > >     https://dpdk.org/browse/dpdk-stable/tag/?id=v16.11.8-rc1
> > > > 
> > > > These patches are located at branch 16.11 of dpdk-stable repo:
> > > >     https://dpdk.org/browse/dpdk-stable/
> > > > 
> > > > Thanks.
> > > > 
> > > > Luca Boccassi
> > > 
> > > Hi,
> > > 
> > > Regression tests from Intel have highlighted a possible issue with
> > > the
> > > changes (unidentified as of now), so while investigation is in
> > > progress
> > > we decided to postpone the release to Monday the 27th to be on the
> > > safe
> > > side.
> > > Apologies for any issues this might cause.
> > 
> > Hi,
> > 
> > Unfortunately triaging is still in progress, so it's better to
> > postpone
> > again, to Wednesday the 29th of August.
> > Apologies again for any issues due to this delay.
> 
> Hello all,
> 
> I've pushed an -rc2 with the following additional changes:
> 
> Luca Boccassi (1):
>       Revert "net/i40e: fix packet count for PF"
> 
> Radu Nicolau (3):
>       net/null: add MAC address setting fake operation
>       test/virtual_pmd: add MAC address setting fake op
>       test/bonding: assign non-zero MAC to null devices
> 
> Radu, I cherry-picked the following 3 patches that you got merged in
> 18.02 as they are necessary to fix bonding regression tests from Intel:
> 
> c5ac7748fd6bfd86b6fb4432b6792733cf32c94c
> c23fc36284e26fca9b52641118ad76a4da99d7af
> e8df563bac263e55b7dd9d45a00417aa92ef66cb
> 
> Qi, I have reverted the following patch that was backported to 16.11.4
> as it breaks a Fortville regression test from Intel:
> 
> 4bf705a7d74b0b4c1d82ad0821c43e32be15a5e5.
> 
> Marco, is there any chance you've got time today to re-run your tests?
> These changes in rc2 have been blessed by Intel and AT&T, so if it
> works for you as well I can then release later tonight.
> 
> A release candidate tarball can be found at:
> 
>     https://dpdk.org/browse/dpdk-stable/tag/?id=v16.11.8-rc2
> 
> These patches are located at branch 16.11 of dpdk-stable repo:
>     https://dpdk.org/browse/dpdk-stable/
> 
> Thanks!
> 

  parent reply	other threads:[~2018-08-29 13:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 18:21 luca.boccassi
2018-08-20  6:46 ` [dpdk-dev] [dpdk-stable] " Marco Varlese
2018-08-20  8:46   ` Luca Boccassi
2018-08-20  8:46 ` [dpdk-dev] " Luca Boccassi
2018-08-23  8:55 ` Luca Boccassi
2018-08-27 16:17   ` Luca Boccassi
2018-08-29  9:55     ` Luca Boccassi
2018-08-29 10:58       ` Marco Varlese
2018-08-29 13:28       ` Marco Varlese [this message]
2018-08-29 13:36         ` [dpdk-dev] [dpdk-stable] " Luca Boccassi

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=af9d1825a4e204669931366fb87344b9e2f6bb20.camel@suse.de \
    --to=mvarlese@suse.de \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=radu.nicolau@intel.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).