please help backporting some patches to stable release 22.11.9

luca.boccassi at gmail.com luca.boccassi at gmail.com
Mon Jul 14 17:13:36 CEST 2025


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 22.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 22.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 07/21/25.

You can find the a temporary work-in-progress branch of the coming 22.11.9
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 22.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 22.11'

Send the backported patch to "stable at dpdk.org" but not "dev at dpdk.org".

FYI, branch 22.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Luca Boccassi

---
5a117f05fc  David Marchand   net/virtio: revert Tx free threshold fix
a1851465f8  Jiawen Wu        net/txgbe: fix to create FDIR filter for tunnel packet
4e12258d78  Stephen Hemminger latencystats: fix receive sample race
5f9223611f  Viacheslav Ovsiienko net/mlx5: fix out-of-order completions in ordinary Rx burst


More information about the stable mailing list