please help backporting some patches to stable release 24.11.3
Kevin Traynor
ktraynor at redhat.com
Mon Jul 21 18:06:03 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 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 07/28/25.
You can find the a temporary work-in-progress branch of the coming 24.11.3
release at:
https://github.com/kevintraynor/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.
Kevin
---
b4ce09b852 Bruce Richardson net/ixgbe/base: fix lock checker errors
25e35296b5 Sunil Kumar Kori net/cnxk: fix reconfiguring MAC address
9843181aa5 Rajesh Mudimadugula crypto/virtio: fix driver ID
a1efd31b0f Nithinsen Kaithakadan common/cnxk: fix AES-CTR salt handling
99c065da47 Dengdui Huang net/hns3: fix Rx packet without CRC data
98cf04bb90 Kiran Kumar K test/graph: fix second run
4cd8c72f66 Bruce Richardson net/ice: fix inconsistency in Rx queue VLAN tag placement (struct ci_rx_queue does not exist in 24.11)
More information about the stable
mailing list