Re: please help backporting some patches to stable release 22.11.9

[David Marchand <david.marchand@redhat.com>]

Hi Luca,

On Mon, Jul 14, 2025 at 5:13 PM <luca.boccassi@gmail.com> 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 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@dpdk.org" but not "dev@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

There is nothing to revert in 22.11 if you did not backport
3e3c7f3fa5ac ("net/virtio: fix check of threshold for Tx freeing").


-- 
David Marchand