please help backporting some patches to stable release 21.11.1
Kevin Traynor
ktraynor at redhat.com
Mon Mar 21 17:02:27 CET 2022
Hi commit authors (and maintainers),
I didn't apply following commits from DPDK main to 21.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 21.11 branch, or
- Indicate that the patch should not be backported
Please do either of the above by 03/23/22.
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 21.11] foo/bar: fix baz
With git format-patch, this can be achieved by appending the parameter:
--subject-prefix='PATCH 21.11'
Send the backported patch to "stable at dpdk.org" but not "dev at dpdk.org".
FYI, branch 21.11 is located at tree:
https://git.dpdk.org/dpdk-stable
Thanks.
Kevin
---
a501609ea6 Pablo de Lara crypto/ipsec_mb: fix length and offset settings
837269c2e5 Pablo de Lara crypto/ipsec_mb: fix GMAC parameters setting
68f8a52a6b Rakesh Kudurumalla net/cnxk: fix build with optimization
More information about the stable
mailing list