please help backporting some patches to stable release 20.11.5
luca.boccassi at gmail.com
luca.boccassi at gmail.com
Wed Mar 9 17:38:04 CET 2022
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 20.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 20.11 branch, or
- Indicate that the patch should not be backported
Please do either of the above by 03/16/22.
You can find the a temporary work-in-progress branch of the coming 20.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 20.11] foo/bar: fix baz
With git format-patch, this can be achieved by appending the parameter:
--subject-prefix='PATCH 20.11'
Send the backported patch to "stable at dpdk.org" but not "dev at dpdk.org".
Thanks.
Luca Boccassi
---
dc065d6efd Adham Masarwah net/mlx5: fix destroying empty matchers list
655c3c26c1 Dmitry Kozlyuk net/mlx5: fix initial link status detection
17f95513ad Dmitry Kozlyuk net/mlx5: fix link status change detection
4bab7ea60c Karl Bonde Torp build: fix build on FreeBSD with Meson 0.61.1
9267617bb0 Shun Hao net/mlx5: fix meter policy creation assert
20659eb380 Wei Huang raw/ifpga: fix interrupt handle allocation
More information about the stable
mailing list