please help backporting some patches to stable release 21.11.1
Kevin Traynor
ktraynor at redhat.com
Tue Mar 8 15:51:11 CET 2022
Reminder of patches that need author rebase for 21.11.1 :-)
On 01/03/2022 11:21, Kevin Traynor wrote:
> 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 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/07/22.
>
> You can find the a temporary work-in-progress branch of the coming 21.11.1
> 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 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
>
> ---
> 315d14d705 Gowrishankar Muthukrishnan event/cnxk: fix memory leaks
> 3cebc8f35f Satheesh Paul net/cnxk: fix Rx/Tx function update
> 52ade97e36 Xuan Ding vhost: fix physical address mapping
>
More information about the stable
mailing list