please help backporting some patches to stable release 20.11.10

Power, Ciara ciara.power at intel.com
Tue Nov 21 15:23:37 CET 2023


Hi Luca,

> -----Original Message-----
> From: luca.boccassi at gmail.com <luca.boccassi at gmail.com>
> Sent: Wednesday, November 15, 2023 11:47 AM
> To: dpdk stable <stable at dpdk.org>
> Cc: Akhil Goyal <gakhil at marvell.com>; Ashish Gupta
> <ashish.gupta at caviumnetworks.com>; Power, Ciara
> <ciara.power at intel.com>; Doherty, Declan <declan.doherty at intel.com>; Fan
> Zhang <roy.fan.zhang at intel.com>; Gowrishankar Muthukrishnan
> <gmuthukrishn at marvell.com>; Ji, Kai <kai.ji at intel.com>; Shally Verma
> <shally.verma at caviumnetworks.com>; Sunila Sahu
> <sunila.sahu at caviumnetworks.com>
> Subject: please help backporting some patches to stable release 20.11.10
> 
> 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 20.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 20.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 2023/11/22.
> 
> You can find the a temporary work-in-progress branch of the coming 20.11.10
> release at:
>     https://github.com/bluca/dpdk-stable
> 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 20.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 20.11'
> 
> Send the backported patch to "stable at dpdk.org" but not "dev at dpdk.org".
> 
> FYI, branch 20.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Luca Boccassi
> 
> ---
> 47a85dda3f  Ciara Power      crypto/openssl: fix memory leaks in asym session

This one doesn't need to be backported to 20.11 - it relates to OpenSSL 3 specific code which wasn't supported in that release.


> 9d91c3047d  Gowrishankar Muthukrishnan crypto/openssl: fix memory leaks
> in asym operations


More information about the stable mailing list