[dpdk-stable] please help backporting some patches to LTS release 16.11.5
Olivier Matz
olivier.matz at 6wind.com
Wed Feb 14 09:46:24 CET 2018
Hi Luca,
On Wed, Feb 07, 2018 at 07:14:28PM +0000, luca.boccassi at gmail.com wrote:
> Hi commit authors (and maintainers),
>
> I didn't manage to apply following commits from upstream to stable branch
> 16.11: conflict happens. I'm wondering can the authors check the following
> list and backport those patches belong to you?
>
> FYI, branch 16.11 is located at tree:
> git://dpdk.org/dpdk-stable
>
> It'd be great if you could do that in one or two weeks. Also, please add a
> heading line like below before the commit log body:
> [ backported from upstream commit xxx ]
>
> Example: http://dpdk.org/browse/dpdk-stable/commit/?h=16.07&id=c4831394c7d1944d8ec27d52c22997f20d19718e
>
> Please let me know if you have any comments, say, need more time, or it's
> worthless to packport it. And please send it to "stable at dpdk.org", but not
> "dev at dpdk.org".
>
> Thanks.
>
> Luca Boccassi
[...]
> 0bf876008 Xueming Li cmdline: avoid garbage in unused fields of parsed result
> 2acf7432a Xueming Li cmdline: fix dynamic tokens parsing
These 2 patches do not need to be backported in 16.11. The first one
is a minor bug that has almost no impact (unused fields not zeroed in
the structure after parsing a command). The second one fixes a feature
that was introduced after 16.11.
More information about the stable
mailing list