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@dpdk.org" but not "dev@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
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@gmail.com <luca.boccassi@gmail.com>
> Sent: Thursday, July 15, 2021 11:05 PM
> Cc: Ajit Khaparde (ajit.khaparde@broadcom.com)
> <ajit.khaparde@broadcom.com>; Churchill Khangar
> <churchill.khangar@intel.com>; Cristian Dumitrescu
> <cristian.dumitrescu@intel.com>; David Christensen
> <david.christensen@broadcom.com>; David Hunt <david.hunt@intel.com>;
> Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>; Jie Zhou <jizh@microsoft.com>;
> Matan Azrad <matan@nvidia.com>; Narcisa Vasile
> <navasile@linux.microsoft.com>; Ori Kam <orika@nvidia.com>; Pallavi
> Kadam <pallavi.kadam@intel.com>; Ranjit Menon
> <ranjit.menon@intel.com>; Richael Zhuang <Richael.Zhuang@arm.com>;
> Shahaf Shuler <shahafs@nvidia.com>; Somnath Kotur
> <somnath.kotur@broadcom.com>; Steeven Li <steeven.li@broadcom.com>;
> Stephen Hurd <stephen.hurd@broadcom.com>; Tyler Retzlaff
> <roretzla@linux.microsoft.com>; Venkata Suresh Kumar P
> <venkata.suresh.kumar.p@intel.com>; Viacheslav Ovsiienko
> <viacheslavo@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@dpdk.org" but not "dev@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
[-- Attachment #1: Type: text/plain, Size: 2176 bytes --] On Thu, Jul 15, 2021 at 8:34 PM <luca.boccassi@gmail.com> wrote: > > 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@dpdk.org" but not "dev@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 Just FYI i have backported this patch and sent it out to stable just now Luca > c150dff40d Viacheslav Ovsiienko net/mlx5: fix Rx queue timestamp format
On Fri, 2021-07-16 at 06:12 +0000, Richael Zhuang wrote: > 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 Ok, thanks. > > -----Original Message----- > > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com> > > Sent: Thursday, July 15, 2021 11:05 PM > > Cc: Ajit Khaparde (ajit.khaparde@broadcom.com) > > <ajit.khaparde@broadcom.com>; Churchill Khangar > > <churchill.khangar@intel.com>; Cristian Dumitrescu > > <cristian.dumitrescu@intel.com>; David Christensen > > <david.christensen@broadcom.com>; David Hunt <david.hunt@intel.com>; > > Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>; Jie Zhou <jizh@microsoft.com>; > > Matan Azrad <matan@nvidia.com>; Narcisa Vasile > > <navasile@linux.microsoft.com>; Ori Kam <orika@nvidia.com>; Pallavi > > Kadam <pallavi.kadam@intel.com>; Ranjit Menon > > <ranjit.menon@intel.com>; Richael Zhuang <Richael.Zhuang@arm.com>; > > Shahaf Shuler <shahafs@nvidia.com>; Somnath Kotur > > <somnath.kotur@broadcom.com>; Steeven Li <steeven.li@broadcom.com>; > > Stephen Hurd <stephen.hurd@broadcom.com>; Tyler Retzlaff > > <roretzla@linux.microsoft.com>; Venkata Suresh Kumar P > > <venkata.suresh.kumar.p@intel.com>; Viacheslav Ovsiienko > > <viacheslavo@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@dpdk.org" but not "dev@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
Hi, Luca
This patch:
"c150dff40d Viacheslav Ovsiienko net/mlx5: fix Rx queue timestamp format"
is not needed for 20.11LTS, the fix is already merged as part of:
8db55d6a "net/mlx5: fix receiving queue timestamp format"
(it was dedicated patch for 20.11LTS, refers to the correct commit in Upstream)
With best regards,
Slava
> -----Original Message-----
> From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> Sent: Thursday, July 15, 2021 18:05
> Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>; Churchill Khangar
> <churchill.khangar@intel.com>; Cristian Dumitrescu
> <cristian.dumitrescu@intel.com>; David Christensen
> <david.christensen@broadcom.com>; David Hunt <david.hunt@intel.com>;
> Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>; Jie Zhou
> <jizh@microsoft.com>; Matan Azrad <matan@nvidia.com>; Narcisa Vasile
> <navasile@linux.microsoft.com>; Ori Kam <orika@nvidia.com>; Pallavi
> Kadam <pallavi.kadam@intel.com>; Ranjit Menon
> <ranjit.menon@intel.com>; Richael Zhuang <richael.zhuang@arm.com>;
> Shahaf Shuler <shahafs@nvidia.com>; Somnath Kotur
> <somnath.kotur@broadcom.com>; Steeven Li <steeven.li@broadcom.com>;
> Stephen Hurd <stephen.hurd@broadcom.com>; Tyler Retzlaff
> <roretzla@linux.microsoft.com>; Venkata Suresh Kumar P
> <venkata.suresh.kumar.p@intel.com>; Slava Ovsiienko
> <viacheslavo@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@dpdk.org" but not "dev@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
On Tue, 2021-07-20 at 15:26 +0000, Slava Ovsiienko wrote:
> Hi, Luca
>
> This patch:
>
> "c150dff40d Viacheslav Ovsiienko net/mlx5: fix Rx queue timestamp format"
>
> is not needed for 20.11LTS, the fix is already merged as part of:
> 8db55d6a "net/mlx5: fix receiving queue timestamp format"
> (it was dedicated patch for 20.11LTS, refers to the correct commit in Upstream)
>
> With best regards,
> Slava
Ok, thanks for confirming.
--
Kind regards,
Luca Boccassi
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 08/02/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@dpdk.org" but not "dev@dpdk.org". FYI, branch 20.11 is located at tree: https://git.dpdk.org/dpdk-stable Thanks. Luca Boccassi --- a1fcde8c80 Michael Baum regex/mlx5: fix leak on device removal 29ca3215f3 Michael Baum regex/mlx5: fix memory region unregistration d81cea5280 Satheesh Paul net/cnxk: fix default MCAM allocation size 0a37b22875 Wenjun Wu net/ice/base: revert change of first profile mask