please help backporting some patches to stable release 23.11.6

[Shani Peretz]

> -----Original Message-----
> From: Richardson, Bruce <bruce.richardson at intel.com>
> Sent: Monday, 5 January 2026 10:49
> To: Shani Peretz <shperetz at nvidia.com>; dpdk stable <stable at dpdk.org>;
> skori at marvell.com
> Subject: RE: please help backporting some patches to stable release 23.11.6
> 
> External email: Use caution opening links or attachments
> 
> 
> > -----Original Message-----
> > From: Shani Peretz <shperetz at nvidia.com>
> > Sent: Tuesday, December 30, 2025 11:07 AM
> > To: dpdk stable <stable at dpdk.org>; Richardson, Bruce
> > <bruce.richardson at intel.com>; skori at marvell.com
> > Subject: RE: please help backporting some patches to stable release
> > 23.11.6
> >
> >
> >
> > > -----Original Message-----
> > > From: Shani Peretz <shperetz at nvidia.com>
> > > Sent: Thursday, 25 December 2025 11:54
> > > To: dpdk stable <stable at dpdk.org>
> 
> <snip>
> 
> > > 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/31/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
> > >
> > > ---
> > > 8a8c02d2bb  Anatoly Burakov  vfio: fix custom containers in
> > > multiprocess
> >
> > > bd96307d15  Bruce Richardson net/fm10k: fix Tx packet prepare
> > > 19d7188f6f Bruce Richardson net/ixgbe: fix Tx packet prepare
> > > 743bbd3bd2  Sunil Kumar Kori net/ice: fix Tx packet prepare
> >
> > Hey Bruce/ Sunil,
> >
> > I noticed that the patches were dropped from the 24.11 release and
> > wanted to make sure it's okay to drop them from 23.11 as well.
> >
> > Thanks,
> > Shani
> >
> Yes, I think that should be fine.
> 
> /Bruce

Thanks Bruce, I'll remove them from need to backport list