Hi Luca, 874312e261 does not need to be backported to 24.11, as the issue it fixes only manifests when running cryptodev testing (which has only been added during DPDK 26.03).
On Thu, Mar 26, 2026 at 9:00 AM <[email protected]> wrote: > 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 24.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 24.11 branch, or > - Indicate that the patch should not be backported > > Please do either of the above by 2026/04/01. > > You can find the a temporary work-in-progress branch of the coming 24.11.5 > 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 24.11] foo/bar: fix baz > > With git format-patch, this can be achieved by appending the parameter: > --subject-prefix='PATCH 24.11' > > Send the backported patch to "[email protected]" but not "[email protected]". > > FYI, branch 24.11 is located at tree: > https://git.dpdk.org/dpdk-stable > > Thanks. > > Luca Boccassi > > --- > 874312e261 Patrick Robb dts: avoid resources conflict on quick > stop/start > bc15a33eee Vipin Varghese doc: update AMD EPYC guide >
