please help backporting some patches to stable release 24.11.7
Luca Boccassi
luca.boccassi at gmail.com
Sun Jul 19 16:03:50 CEST 2026
If you want your patch to be included in the 24.11.x release, backport
it to the 24.11 branch, test it, and then send it to stable at dpdk.org
using --subject-prefix='PATCH 24.11'
On Sat, 18 Jul 2026 at 10:19, Maxime Peim <maxime.peim at gmail.com> wrote:
>
> Hi Luca,
>
> Sorry I missed your email and I am late to backport my patch, what should I do then please?
>
> Best regards,
> Maxime Peim
>
> On Mon, Jul 6, 2026 at 12:27 PM <luca.boccassi at 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 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/07/10.
>>
>> You can find the a temporary work-in-progress branch of the coming 24.11.7
>> 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 "stable at dpdk.org" but not "dev at dpdk.org".
>>
>> FYI, branch 24.11 is located at tree:
>> https://git.dpdk.org/dpdk-stable
>>
>> Thanks.
>>
>> Luca Boccassi
>>
>> ---
>> ece7d7eef0 Anurag Mandal net/iavf: fix duplicate VF reset during PF reset recovery
>> 8e038dee42 Bruce Richardson net/idpf: fix Tx of large mbuf segments
>> edff93f638 Dakota Sicher net/bnxt: skip timed Tx pacing setup when unsupported
>> 1c39f3f240 Marat Khalili bpf/validate: fix BPF_JMP empty range handling
>> 7f8ce8d13f Marat Khalili bpf/validate: fix EBPF_JSLT | BPF_X evaluation
>> b482a764c6 Maxime Peim eal: fix index for non-EAL lcores
>> 26e7538e00 Zaiyu Wang net/txgbe: fix link flow control config for Sapphire
>> e586adbac0 Zaiyu Wang net/txgbe: fix mass of unknown interrupts
More information about the stable
mailing list