please help backporting some patches to stable release 23.11.6

Richardson, Bruce bruce.richardson at intel.com
Mon Dec 22 09:42:13 CET 2025



> -----Original Message-----
> From: Shani Peretz <shperetz at nvidia.com>
> Sent: Sunday, December 21, 2025 4:26 PM
> Cc: Burakov, Anatoly <anatoly.burakov at intel.com>; Andrew Rybchenko
> <andrew.rybchenko at oktetlabs.ru>; Ankit Garg <nktgrg at google.com>;
> Richardson, Bruce <bruce.richardson at intel.com>; Chengwen Feng
> <fengchengwen at huawei.com>; Loftus, Ciara <ciara.loftus at intel.com>;
> Cunming Liang <cunming.liang at intel.com>; Dariusz Sosnowski
> <dsosnowski at nvidia.com>; Marchand, David
> <david.marchand at redhat.com>; Gagandeep Singh <g.singh at nxp.com>;
> Haiyue Wang <haiyue.wang at intel.com>; Hemant Agrawal
> <hemant.agrawal at nxp.com>; Nagarahalli, Honnappa
> <Honnappa.Nagarahalli at arm.com>; Jasper Tran O'Leary
> <jtranoleary at google.com>; Jeroen de Borst <jeroendb at google.com>; Joshua
> Washington <joshwash at google.com>; Junfeng Guo <junfengg at nvidia.com>;
> Konstantin Ananyev <konstantin.v.ananyev at yandex.ru>; Matan Azrad
> <matan at nvidia.com>; Michael Baum <michaelba at nvidia.com>; Morten
> Brørup <mb at smartsharesystems.com>; Nawal Kishor
> <nkishor at marvell.com>; Ori Kam <orika at nvidia.com>; Robin Jarry
> <rjarry at redhat.com>; Rongwei Liu <rongweil at nvidia.com>; Rushil Gupta
> <rushilg at google.com>; Sachin Saxena <sachin.saxena at nxp.com>; Gobriel,
> Sameh <sameh.gobriel at intel.com>; Shreyansh Jain
> <shreyansh.jain at nxp.com>; Suanming Mou <suanmingm at nvidia.com>;
> Thomas Monjalon <thomas at monjalon.net>; Vamsi Attunuru
> <vattunuru at marvell.com>; Viacheslav Ovsiienko <viacheslavo at nvidia.com>;
> Medvedkin, Vladimir <vladimir.medvedkin at intel.com>; Xiaoyun Li
> <xiaoyun.li at intel.com>; Wang, Yipeng1 <yipeng1.wang at intel.com>; Zhe Tao
> <zhe.tao at intel.com>
> Subject: please help backporting some patches to stable release 23.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 23.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 23.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 12/28/25.
> 
> You can find the a temporary work-in-progress branch of the coming 23.11.6
> release at:
>     https://github.com/shanipr/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 23.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 23.11'
> 
> Send the backported patch to "stable at dpdk.org" but not "dev at dpdk.org".
> 
> FYI, branch 23.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Shani
> 
> ---
> b74d638ab9  Bruce Richardson test/func_reentrancy: fix args to EAL init call

Since this is a patch to unit tests only, and hasn't been causing us any issues before, I don't think we need it backported.

/Bruce


More information about the stable mailing list