please help backporting some patches to stable release 21.11.6

[Kevin Traynor]

On 12/12/2023 09:52, Power, Ciara wrote:
> 
> 
>> -----Original Message-----
>> From: Kevin Traynor <ktraynor at redhat.com>
>> Sent: Thursday, December 7, 2023 11:38 AM
>> To: dpdk stable <stable at dpdk.org>
>> Cc: Gujjar, Abhinandan S <abhinandan.gujjar at intel.com>; Akhil Goyal
>> <gakhil at marvell.com>; Amit Prakash Shukla <amitprakashs at marvell.com>;
>> Burakov, Anatoly <anatoly.burakov at intel.com>; Anoob Joseph
>> <anoobj at marvell.com>; Ashwin Sekhar T K <asekhar at marvell.com>; Bing
>> Zhao <bingz at nvidia.com>; Chaoyong He <chaoyong.he at corigine.com>;
>> Power, Ciara <ciara.power at intel.com>; Walsh, Conor
>> <conor.walsh at intel.com>; Marchand, David <david.marchand at redhat.com>;
>> Ferruh Yigit <ferruh.yigit at amd.com>; Kundapura, Ganapati
>> <ganapati.kundapura at intel.com>; Gowrishankar Muthukrishnan
>> <gmuthukrishn at marvell.com>; Hanumanth Pothula
>> <hpothula at marvell.com>; Harman Kalra <hkalra at marvell.com>; Hemant
>> Agrawal <hemant.agrawal at nxp.com>; Honnappa Nagarahalli
>> <honnappa.nagarahalli at arm.com>; Jerin Jacob <jerinj at marvell.com>; Jiawen
>> Wu <jiawenwu at trustnetic.com>; Jie Hai <haijie1 at huawei.com>; Ji, Kai
>> <kai.ji at intel.com>; Kaisen You <kaisenx.you at intel.com>; Deng, KaiwenX
>> <kaiwenx.deng at intel.com>; Kiran Kumar K <kirankumark at marvell.com>;
>> Matan Azrad <matan at nvidia.com>; Michael Baum <michaelba at nvidia.com>;
>> Ye, MingjinX <mingjinx.ye at intel.com>; Mohammad Iqbal Ahmad
>> <mahmad at marvell.com>; Morten Brørup <mb at smartsharesystems.com>;
>> Nithin Dabilpuram <ndabilpuram at marvell.com>; Matz, Olivier
>> <olivier.matz at 6wind.com>; Ori Kam <orika at nvidia.com>; Pavan Nikhilesh
>> <pbhagavatula at marvell.com>; Zhang, Qi Z <qi.z.zhang at intel.com>; Rahul
>> Bhansali <rbhansali at marvell.com>; Ruifeng Wang <ruifeng.wang at arm.com>;
>> Shijith Thotton <sthotton at marvell.com>; Srujana Challa
>> <schalla at marvell.com>; Stephen Hemminger
>> <stephen at networkplumber.org>; Steve Yang <stevex.yang at intel.com>;
>> Suanming Mou <suanmingm at nvidia.com>; Sunil Kumar Kori
>> <skori at marvell.com>; Tyler Retzlaff <roretzla at linux.microsoft.com>; Vamsi
>> Attunuru <vattunuru at marvell.com>; Viacheslav Ovsiienko
>> <viacheslavo at nvidia.com>
>> Subject: please help backporting some patches to stable release 21.11.6
>>
>> 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 21.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 21.11 branch, or
>>      - Indicate that the patch should not be backported
>>
>> Please do either of the above by 12/12/23.
>>
>> You can find the a temporary work-in-progress branch of the coming 21.11.6
>> release at:
>>      https://github.com/kevintraynor/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 21.11] foo/bar: fix baz
>>
>> With git format-patch, this can be achieved by appending the parameter:
>>      --subject-prefix='PATCH 21.11'
>>
>> Send the backported patch to "stable at dpdk.org" but not "dev at dpdk.org".
>>
>> FYI, branch 21.11 is located at tree:
>>     https://git.dpdk.org/dpdk-stable
>>
>> Thanks.
>>
>> Kevin
>>
>> ---
>> 2e9863fbb6  Akhil Goyal      common/cnxk: fix different size bit operations
>> 4f6f36ce23  Akhil Goyal      common/cnxk: fix leak in error path
>> d2d7f0190b  Akhil Goyal      doc: fix code blocks in cryptodev guide
>> 3dd3115078  Amit Prakash Shukla dma/cnxk: fix chunk buffer failure return
>> code
>> 95a955e3e0  Amit Prakash Shukla dma/cnxk: fix device reconfigure
>> 63bf81a617  Anatoly Burakov  test: fix named test macro
>> c5b531d6ee  Anoob Joseph     app/crypto-perf: fix session freeing
>> 6df1bc6b3b  Ashwin Sekhar T K mempool/cnxk: avoid hang when counting
>> batch allocs b3ddd649ad  Ashwin Sekhar T K mempool/cnxk: fix alloc from
>> non-EAL threads
>> 37ca457d3f  Bing Zhao        common/mlx5: fix obtaining IB device in LAG mode
>> 2ece3b7186  Bing Zhao        net/mlx5: fix flow workspace double free in
>> Windows
>> 47a85dda3f  Ciara Power      crypto/openssl: fix memory leaks in asym session
> 
> Hi Kevin,
> 
> These fixes relate to Openssl 3 codepaths that didn't exist in 21.11.
> Fix does not need backporting.
> 

ok, thanks for letting me know. Dropped it.
Kevin.

> Thanks,
> Ciara
> 
> 
>