please help backporting some patches to stable release 22.11.6
luca.boccassi at gmail.com
luca.boccassi at gmail.com
Tue Jun 25 02:04:42 CEST 2024
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 2024/07/01.
You can find the a temporary work-in-progress branch of the coming 22.11.6
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
---
ecf408d2aa Bing Zhao app/testpmd: fix indirect action flush
b9a87346b0 Chengwen Feng ethdev: fix strict aliasing in link up
0f9ec0cbd2 Kaiwen Deng net/iavf: fix VF reset when using DCF
590ee5cd95 Nithin Dabilpuram net/cnxk: update SA userdata and keep original cookie
4c2f14bc6d Sunil Kumar Kori net/cnxk: fix xstats reset
More information about the stable
mailing list