[dpdk-stable] please help backporting some patches to stable release 19.11.3

[Ferruh Yigit]

On 5/27/2020 11:14 AM, luca.boccassi at gmail.com wrote:
> Hi commit authors (and maintainers),
> 
> I didn't apply following commits from DPDK master to 19.11
> stable branch, as conflicts or build errors occur.
> 
> Can authors check your patches in the following list and either:
>     - Backport your patches to the 19.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by June the 3rd.
> 
> 
> Some notes on stable backports:
> 
> A backport should contain a reference to the DPDK master branch commit
> in it's commit message in the following fashion:
>     [ upstream commit <commit's dpdk master branch SHA-1 checksum> ]
> 
> For example:
>     https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb
> 
> When sending the backported patch, please indicate the target branch in the
> subject line, as we have multiple branches, for example:
>     [PATCH 19.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 19.11'
> 
> Send the backported patch to "stable at dpdk.org" but not "dev at dpdk.org".
> 
> FYI, branch 19.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Luca Boccassi
> 

<...>

> 867b49d17a  Ferruh Yigit     ring: fix build for gcc O1 optimization

Hi Luca,

The fix is not applicable for 19.11, we can ignore it.

'lib/librte_ring/rte_ring_peek.h' has been added for 20.05 and this patch fixes it.