Skip to contentSkip to conversation

please help backporting some patches to stable release 24.11.5

DISCUSSION [email protected] 2 participants 2 messages Feb 20

lore
Share & tools
lore
#0 lore raw

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 02/27/26.

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

---

f82b3ed6ab  Anatoly Burakov  net/ixgbe: fix pointer handling in IPsec
ab797d5bcf  Bruce Richardson dma/idxd: mark portal pointer as volatile
77bb34e047  Ivan Malov       net/sfc: avoid speed reset when setting FEC in started state
e0f92e31f7  Kishore Padmanabha net/bnxt: fix statistics for high number of queues
bd2f563dbd  Rahul Bhansali   common/cnxk: fix duplicated branches
2e79349dcd  Song Yoong Siang net/e1000: fix igc launch time calculation
#1 lore raw

Hi Luca,

The patch e0f92e31f7 is not required to be backported to 24.11. There has changes in that part of code that will not allow simple merge of this fix. This fix is not critical to be ported to older version as it is fixing stats counters in a specific scenario.

Thanks,
Kishore

-----Original Message-----
From: [email protected] <[email protected]>
Sent: Friday, February 20, 2026 10:41 AM
To: dpdk <[email protected]>
Cc: dpdk stable <[email protected]>
Subject: please help backporting some patches to stable release 24.11.5

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 02/27/26.

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=d90e6ae6f936ecdc2fd381
1ff9f26aec7f3c06eb

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

---

f82b3ed6ab  Anatoly Burakov  net/ixgbe: fix pointer handling in IPsec
ab797d5bcf  Bruce Richardson dma/idxd: mark portal pointer as volatile
77bb34e047  Ivan Malov       net/sfc: avoid speed reset when setting FEC

in started state
e0f92e31f7 Kishore Padmanabha net/bnxt: fix statistics for high number of queues
bd2f563dbd Rahul Bhansali common/cnxk: fix duplicated branches
2e79349dcd Song Yoong Siang net/e1000: fix igc launch time calculation