From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f52.google.com (mail-wr1-f52.google.com [209.85.221.52]) by dpdk.org (Postfix) with ESMTP id 750A8F11; Wed, 29 Aug 2018 11:55:45 +0200 (CEST) Received: by mail-wr1-f52.google.com with SMTP id n2-v6so4191831wrw.7; Wed, 29 Aug 2018 02:55:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:mime-version; bh=fUCP5qGarzrG3BBnPfNntPiRCscvokXJc3Tih4eiZwY=; b=bw1HSVY+JwmFIB5nxsa6p/rQ0B6DfAE3bqYyU9v3YZfq76G+sz+Xw+7X0C6PGDpOxV VIPe6rOth7WIL+IdJSQdYxfWllA3cl9cf/D4hWdmOaZGrBIUD5smUV6F2P52XcxG5Xtt 3zJy0DO1xTvFzy0cQ3FVm42jUIBvB7rWt/wV5SltIpx4ezRZRbM9R/ruQgcisakauNna nYKNRq5nWhhzMd7SdaUbtEUVSUhrCUn1EfrmPdk5iSRyVS1LwUbPnRF0LaKoxZbAym7U Iitb6Sm2zvIoB5v+XJRx7b3KsudZpXvu2VyKhLZk0u4/ySlxmSjkmxCxpV8UNDwYVlLR M25Q== X-Gm-Message-State: APzg51C+Fcm0dSQ6fqDNTwJJ9RhN3EcxlQu56EBjn3oMtOlm1mYyFL97 ZYbPzXWeK2Dl4UXbWTdOP0XPaYsj3AQsWg== X-Google-Smtp-Source: ANB0Vdbt3JAa7K5Xy0+uBBv/wsaBA4u+ShhkvlobDvICY2+IJ60i1Mq3tX1UdSNrAn4b66HoQz8T7w== X-Received: by 2002:a5d:6150:: with SMTP id y16-v6mr3895380wrt.141.1535536544763; Wed, 29 Aug 2018 02:55:44 -0700 (PDT) Received: from localhost ([2001:1be0:110d:fcfe:41aa:5bfa:6cf3:7531]) by smtp.gmail.com with ESMTPSA id j20-v6sm2312134wmh.9.2018.08.29.02.55.43 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 29 Aug 2018 02:55:43 -0700 (PDT) Message-ID: <1535536543.1113.31.camel@debian.org> From: Luca Boccassi To: dpdk stable Cc: dev@dpdk.org, radu.nicolau@intel.com, qi.z.zhang@intel.com, mvarlese@suse.de Date: Wed, 29 Aug 2018 10:55:43 +0100 In-Reply-To: <1535386654.8636.12.camel@debian.org> References: <20180813182103.28045-1-luca.boccassi@gmail.com> <1535014539.5764.128.camel@debian.org> <1535386654.8636.12.camel@debian.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Subject: Re: [dpdk-dev] 16.11.8 (LTS) patches review and test X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Aug 2018 09:55:45 -0000 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, > > >=20 > > > 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. > > >=20 > > > Also for the companies committed to running regression tests, > > > please run the tests and report any issue before the release > > > date. > > >=20 > > > A release candidate tarball can be found at: > > >=20 > > > =C2=A0=C2=A0=C2=A0=C2=A0https://dpdk.org/browse/dpdk-stable/tag/?id= =3Dv16.11.8-rc1 > > >=20 > > > These patches are located at branch 16.11 of dpdk-stable repo: > > > =C2=A0=C2=A0=C2=A0=C2=A0https://dpdk.org/browse/dpdk-stable/ > > >=20 > > > Thanks. > > >=20 > > > Luca Boccassi > >=20 > > Hi, > >=20 > > 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. >=20 > Hi, >=20 > 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=C2=A0well I can then release later tonight. A release candidate tarball can be found at: =C2=A0=C2=A0=C2=A0=C2=A0https://dpdk.org/browse/dpdk-stable/tag/?id=3Dv16.1= 1.8-rc2 These patches are located at branch 16.11 of dpdk-stable repo: =C2=A0=C2=A0=C2=A0=C2=A0https://dpdk.org/browse/dpdk-stable/ Thanks! --=20 Kind regards, Luca Boccassi