please help backporting some patches to stable release 19.11.12

[Richardson, Bruce]

> -----Original Message-----
> From: christian.ehrhardt at canonical.com <christian.ehrhardt at canonical.com>
> Sent: Thursday, March 17, 2022 2:17 PM
> Cc: Singh, Aman Deep <aman.deep.singh at intel.com>; Iremonger, Bernard
> <bernard.iremonger at intel.com>; Richardson, Bruce
> <bruce.richardson at intel.com>; Yigit, Ferruh <ferruh.yigit at intel.com>;
> Gregory Etelson <getelson at nvidia.com>; Wu, Jingjing
> <jingjing.wu at intel.com>; Mcnamara, John <john.mcnamara at intel.com>;
> Kovacevic, Marko <marko.kovacevic at intel.com>; Xu, Ting
> <ting.xu at intel.com>; Lu, Wenzhuo <wenzhuo.lu at intel.com>
> Subject: please help backporting some patches to stable release 19.11.12
> 
> Hi commit authors (and maintainers),
> 
> Despite being selected by the DPDK maintenance tool ./devtools/git-log-
> fixes.sh
> I didn't apply following commits from DPDK main 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 03/20/22.
> 
> You can find the a temporary work-in-progress branch of the coming
> 19.11.12
> release at:
>     https://github.com/cpaelzer/dpdk-stable-queue
> It is recommended to backport on top of that to minimize further conflicts
> or
> misunderstandings.
> 
> Some notes on stable backports:
> 
> A backport should contain a reference to the DPDK main branch commit
> in it's commit message in the following fashion:
>     [ upstream commit <commit's dpdk main 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.
> 
> Christian Ehrhardt <christian.ehrhardt at canonical.com>
> 
> ---
> c265d58619  Bruce Richardson doc: replace characters for (R) symbol in
> Linux guide
> a058de216c  Gregory Etelson  app/testpmd: fix GTP header parsing in
> checksum engine

Hi,

I am not sure that my doc fix is worth backporting. If I get the chance I will do a new version of it, but if it is not backported no serious issues will occur as the docs seem fine without it. It's more a convenience for developers.

/Bruce