[dpdk-stable] please help backporting some patches to stable release 20.11.3
Richael Zhuang
Richael.Zhuang at arm.com
Fri Jul 16 08:12:41 CEST 2021
Hi,
This patch
"29343b9030 Richael Zhuang test/power: fix CPU frequency when turbo enabled" should not be backport. It's based on commit ef1cc88f1837 and 06cffd468fd.
Best Regards,
Richael
> -----Original Message-----
> From: luca.boccassi at gmail.com <luca.boccassi at gmail.com>
> Sent: Thursday, July 15, 2021 11:05 PM
> Cc: Ajit Khaparde (ajit.khaparde at broadcom.com)
> <ajit.khaparde at broadcom.com>; Churchill Khangar
> <churchill.khangar at intel.com>; Cristian Dumitrescu
> <cristian.dumitrescu at intel.com>; David Christensen
> <david.christensen at broadcom.com>; David Hunt <david.hunt at intel.com>;
> Dmitry Kozlyuk <dmitry.kozliuk at gmail.com>; Jie Zhou <jizh at microsoft.com>;
> Matan Azrad <matan at nvidia.com>; Narcisa Vasile
> <navasile at linux.microsoft.com>; Ori Kam <orika at nvidia.com>; Pallavi
> Kadam <pallavi.kadam at intel.com>; Ranjit Menon
> <ranjit.menon at intel.com>; Richael Zhuang <Richael.Zhuang at arm.com>;
> Shahaf Shuler <shahafs at nvidia.com>; Somnath Kotur
> <somnath.kotur at broadcom.com>; Steeven Li <steeven.li at broadcom.com>;
> Stephen Hurd <stephen.hurd at broadcom.com>; Tyler Retzlaff
> <roretzla at linux.microsoft.com>; Venkata Suresh Kumar P
> <venkata.suresh.kumar.p at intel.com>; Viacheslav Ovsiienko
> <viacheslavo at nvidia.com>
> Subject: please help backporting some patches to stable release 20.11.3
>
> Hi commit authors (and maintainers),
>
> 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 07/22/21.
>
> You can find the a temporary work-in-progress branch of the coming 20.11.3
> 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".
>
> FYI, branch 20.11 is located at tree:
> https://git.dpdk.org/dpdk-stable
>
> Thanks.
>
> Luca Boccassi
>
> ---
> b3fa83945a Ajit Khaparde net/bnxt: fix ring allocation and free
> a57d92d73d Cristian Dumitrescu pipeline: fix table entry read
> cfdaa678b3 Dmitry Kozlyuk eal/windows: cleanup interrupt resources
> 3888f31950 Dmitry Kozlyuk eal/windows: fix interrupt thread handle
> leakage
> 35dff5d3b7 Dmitry Kozlyuk eal/windows: fix interrupt thread ID
> 29343b9030 Richael Zhuang test/power: fix CPU frequency when turbo
> enabled
> 03c8f2fe11 Somnath Kotur net/bnxt: detect bad opaque in Rx completion
> c150dff40d Viacheslav Ovsiienko net/mlx5: fix Rx queue timestamp format
More information about the stable
mailing list