From: Luca Boccassi <bluca@debian.org>
To: stable@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] 16.11.7 (LTS) patches review and test
Date: Thu, 14 Jun 2018 11:05:58 +0100 [thread overview]
Message-ID: <1528970758.6554.44.camel@debian.org> (raw)
In-Reply-To: <1528898958.6554.35.camel@debian.org>
On Wed, 2018-06-13 at 15:09 +0100, Luca Boccassi wrote:
> On Fri, 2018-06-08 at 10:17 +0100, Luca Boccassi wrote:
> > On Thu, 2018-05-31 at 11:25 +0100, Luca Boccassi wrote:
> > > Hi all,
> > >
> > > Here is a list of patches targeted for LTS release 16.11.7.
> > > Please
> > > help review and test. The planned date for the final release is
> > > Monday,
> > > June the 11th.
> > > 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.
> > >
> > > These patches are located at branch 16.11 of dpdk-stable repo:
> > > https://dpdk.org/browse/dpdk-stable/
> > >
> > > Thanks.
> > >
> > > Luca Boccassi
> >
> > Hi,
> >
> > The release date for 16.11.7 is being postponed by two days to
> > Wednesday the 13th to due to unforeseen delays in some regression
> > tests. Apologies for the inconvenience.
>
> Hi,
>
> PF performance tests ran by Intel with FVL40g show a small regression
> that is being investigated, so I am postponing the 16.11.7 release to
> tomorrow pending confirmation.
> Apologies for the inconvenience.
The problem appears to be related to the new firmware version (5.05 vs
6.01), and no other issue was found, so all good.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2018-06-14 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 10:25 Luca Boccassi
2018-06-08 9:17 ` Luca Boccassi
2018-06-13 14:09 ` Luca Boccassi
2018-06-14 10:05 ` Luca Boccassi [this message]
2018-06-08 15:27 ` 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=1528970758.6554.44.camel@debian.org \
--to=bluca@debian.org \
--cc=dev@dpdk.org \
--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).