* [dpdk-stable] please help backporting some patches to stable release 20.11.1 [not found] <20210205115222.1287558-1-luca.boccassi@gmail.com> @ 2021-02-05 11:53 ` luca.boccassi 2021-02-09 10:39 ` luca.boccassi 2021-02-19 8:59 ` Ferruh Yigit 0 siblings, 2 replies; 11+ messages in thread From: luca.boccassi @ 2021-02-05 11:53 UTC (permalink / raw) To: dpdk stable 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 2021/02/19. 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 --- c86e930165 Lance Richardson net/bnxt: fix fallback mbuf allocation logic d5be7f9375 Qi Zhang net/ice/base: update add scheduler node counter ^ permalink raw reply [flat|nested] 11+ messages in thread
* [dpdk-stable] please help backporting some patches to stable release 20.11.1 2021-02-05 11:53 ` [dpdk-stable] please help backporting some patches to stable release 20.11.1 luca.boccassi @ 2021-02-09 10:39 ` luca.boccassi 2021-02-12 23:42 ` luca.boccassi ` (2 more replies) 2021-02-19 8:59 ` Ferruh Yigit 1 sibling, 3 replies; 11+ messages in thread From: luca.boccassi @ 2021-02-09 10:39 UTC (permalink / raw) To: dpdk stable 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 02/16/21. 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 --- c27e64ee3e Chengchang Tang net/hns3: fix stats flip overflow 7f2a320df9 Huisong Li net/hns3: fix query order of link status and link info 00984de533 Viacheslav Ovsiienko net/mlx5: fix Tx queue size created with DevX ^ permalink raw reply [flat|nested] 11+ messages in thread
* [dpdk-stable] please help backporting some patches to stable release 20.11.1 2021-02-09 10:39 ` luca.boccassi @ 2021-02-12 23:42 ` luca.boccassi [not found] ` <20210212234341.256656-1-luca.boccassi@gmail.com> 2021-02-18 9:41 ` Luca Boccassi [not found] ` <20210209103924.468111-1-luca.boccassi@gmail.com> 2 siblings, 1 reply; 11+ messages in thread From: luca.boccassi @ 2021-02-12 23:42 UTC (permalink / raw) To: dpdk stable 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 02/19/21. You can find the a temporary work-in-progress branch of the coming 20.11.1 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 --- b9c366e029 Feifei Wang net/ixgbe: fix UDP zero checksum on Arm ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <20210212234341.256656-1-luca.boccassi@gmail.com>]
* Re: [dpdk-stable] please help backporting some patches to stable release 20.11.1 [not found] ` <20210212234341.256656-1-luca.boccassi@gmail.com> @ 2021-02-16 13:08 ` Wang, Haiyue 2021-02-16 13:22 ` Luca Boccassi 0 siblings, 1 reply; 11+ messages in thread From: Wang, Haiyue @ 2021-02-16 13:08 UTC (permalink / raw) To: luca.boccassi; +Cc: Guo, Jia, Laatz, Kevin, Paolo Valerio, dpdk stable Hi Luca, The base of 'b9c366e029 Feifei Wang net/ixgbe: fix UDP zero checksum on Arm' is also in 21.02, so no need to backporting. git describe --contains cf96160a0a95a8a9b99c14a1bf08ce4a417e6922 v21.02-rc1~480 commit cf96160a0a95a8a9b99c14a1bf08ce4a417e6922 Author: Feifei Wang <feifei.wang2@arm.com> Date: Wed Nov 18 04:48:59 2020 -0600 net/ixgbe: enable NEON path with checksum offload IXGBE NEON vector PMD now supports checksum offloading, hence can be used when DEV_RX_OFFLOAD_CHECKSUM is set. BR, Haiyue > -----Original Message----- > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com> > Sent: Saturday, February 13, 2021 07:44 > Cc: Wang, Haiyue <haiyue.wang@intel.com>; Guo, Jia <jia.guo@intel.com>; Laatz, Kevin > <kevin.laatz@intel.com>; Paolo Valerio <pvalerio@redhat.com> > Subject: please help backporting some patches to stable release 20.11.1 > > 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 02/19/21. > > You can find the a temporary work-in-progress branch of the coming 20.11.1 > 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 > > --- > 0d32fd0945 Bruce Richardson telemetry: mark init function as internal-only > b9c366e029 Feifei Wang net/ixgbe: fix UDP zero checksum on Arm ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [dpdk-stable] please help backporting some patches to stable release 20.11.1 2021-02-16 13:08 ` Wang, Haiyue @ 2021-02-16 13:22 ` Luca Boccassi 0 siblings, 0 replies; 11+ messages in thread From: Luca Boccassi @ 2021-02-16 13:22 UTC (permalink / raw) To: Wang, Haiyue; +Cc: Guo, Jia, Laatz, Kevin, Paolo Valerio, dpdk stable On Tue, 2021-02-16 at 13:08 +0000, Wang, Haiyue wrote: > Hi Luca, > > The base of 'b9c366e029 Feifei Wang net/ixgbe: fix UDP zero checksum on Arm' > is also in 21.02, so no need to backporting. > > git describe --contains cf96160a0a95a8a9b99c14a1bf08ce4a417e6922 > v21.02-rc1~480 > > commit cf96160a0a95a8a9b99c14a1bf08ce4a417e6922 > Author: Feifei Wang <feifei.wang2@arm.com> > Date: Wed Nov 18 04:48:59 2020 -0600 > > net/ixgbe: enable NEON path with checksum offload > > IXGBE NEON vector PMD now supports checksum offloading, hence can be > used when DEV_RX_OFFLOAD_CHECKSUM is set. > > > BR, > Haiyue Understood, thank you! > > -----Original Message----- > > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com> > > Sent: Saturday, February 13, 2021 07:44 > > Cc: Wang, Haiyue <haiyue.wang@intel.com>; Guo, Jia <jia.guo@intel.com>; Laatz, Kevin > > <kevin.laatz@intel.com>; Paolo Valerio <pvalerio@redhat.com> > > Subject: please help backporting some patches to stable release 20.11.1 > > > > 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 02/19/21. > > > > You can find the a temporary work-in-progress branch of the coming 20.11.1 > > 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 > > > > --- > > 0d32fd0945 Bruce Richardson telemetry: mark init function as internal-only > > b9c366e029 Feifei Wang net/ixgbe: fix UDP zero checksum on Arm ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [dpdk-stable] please help backporting some patches to stable release 20.11.1 2021-02-09 10:39 ` luca.boccassi 2021-02-12 23:42 ` luca.boccassi @ 2021-02-18 9:41 ` Luca Boccassi 2021-02-18 13:33 ` Xueming(Steven) Li [not found] ` <20210209103924.468111-1-luca.boccassi@gmail.com> 2 siblings, 1 reply; 11+ messages in thread From: Luca Boccassi @ 2021-02-18 9:41 UTC (permalink / raw) To: Xueming Li; +Cc: dpdk stable On Tue, 2021-02-09 at 10:39 +0000, 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 02/16/21. > > > 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 > > --- > c27e64ee3e Chengchang Tang net/hns3: fix stats flip overflow > 7f2a320df9 Huisong Li net/hns3: fix query order of link status and link info > 00984de533 Viacheslav Ovsiienko net/mlx5: fix Tx queue size created with DevX Hi Xueming, Could you please check with Viacheslav if this net/mlx5 backport is needed and if it is going to be sent soon, or if I should proceed without it? Thanks! -- Kind regards, Luca Boccassi ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [dpdk-stable] please help backporting some patches to stable release 20.11.1 2021-02-18 9:41 ` Luca Boccassi @ 2021-02-18 13:33 ` Xueming(Steven) Li 2021-02-18 17:42 ` Luca Boccassi 0 siblings, 1 reply; 11+ messages in thread From: Xueming(Steven) Li @ 2021-02-18 13:33 UTC (permalink / raw) To: Luca Boccassi; +Cc: dpdk stable >-----Original Message----- >From: Luca Boccassi <bluca@debian.org> >Sent: Thursday, February 18, 2021 5:42 PM >To: Xueming(Steven) Li <xuemingl@nvidia.com> >Cc: dpdk stable <stable@dpdk.org> >Subject: Re: please help backporting some patches to stable release 20.11.1 > >On Tue, 2021-02-09 at 10:39 +0000, 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 02/16/21. >> >> >> 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=d90e6ae6f936ecdc2f >> d3811ff9f26aec7f3c06eb >> >> 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 >> >> --- >> c27e64ee3e Chengchang Tang net/hns3: fix stats flip overflow >> 7f2a320df9 Huisong Li net/hns3: fix query order of link status and link info >> 00984de533 Viacheslav Ovsiienko net/mlx5: fix Tx queue size created >> with DevX > >Hi Xueming, > >Could you please check with Viacheslav if this net/mlx5 backport is needed and if it is going to be sent soon, or if I should proceed >without it? Confirmed with Slava, he will send tomorrow. > >Thanks! > >-- >Kind regards, >Luca Boccassi ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [dpdk-stable] please help backporting some patches to stable release 20.11.1 2021-02-18 13:33 ` Xueming(Steven) Li @ 2021-02-18 17:42 ` Luca Boccassi 0 siblings, 0 replies; 11+ messages in thread From: Luca Boccassi @ 2021-02-18 17:42 UTC (permalink / raw) To: Xueming(Steven) Li; +Cc: dpdk stable On Thu, 2021-02-18 at 13:33 +0000, Xueming(Steven) Li wrote: > > -----Original Message----- > > From: Luca Boccassi <bluca@debian.org> > > Sent: Thursday, February 18, 2021 5:42 PM > > To: Xueming(Steven) Li <xuemingl@nvidia.com> > > Cc: dpdk stable <stable@dpdk.org> > > Subject: Re: please help backporting some patches to stable release 20.11.1 > > > > On Tue, 2021-02-09 at 10:39 +0000, 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 02/16/21. > > > > > > > > > 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=d90e6ae6f936ecdc2f > > > d3811ff9f26aec7f3c06eb > > > > > > 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 > > > > > > --- > > > c27e64ee3e Chengchang Tang net/hns3: fix stats flip overflow > > > 7f2a320df9 Huisong Li net/hns3: fix query order of link status and link info > > > 00984de533 Viacheslav Ovsiienko net/mlx5: fix Tx queue size created > > > with DevX > > > > Hi Xueming, > > > > Could you please check with Viacheslav if this net/mlx5 backport is needed and if it is going to be sent soon, or if I should proceed > > without it? > > Confirmed with Slava, he will send tomorrow. Thank you! -- Kind regards, Luca Boccassi ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <20210209103924.468111-1-luca.boccassi@gmail.com>]
* Re: [dpdk-stable] please help backporting some patches to stable release 20.11.1 [not found] ` <20210209103924.468111-1-luca.boccassi@gmail.com> @ 2021-02-20 6:49 ` Huisong Li 0 siblings, 0 replies; 11+ messages in thread From: Huisong Li @ 2021-02-20 6:49 UTC (permalink / raw) To: dpdk stable, luca.boccassi Hi, Luca Boccassi We are celebrating the Spring Festival. Apologies for the delayed reply. Two pacthes of hns3 PMD have been sent. Please check. Thanks Huisong 在 2021/2/9 18:39, luca.boccassi@gmail.com 写道: > 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 02/16/21. > > > 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 > > --- > c27e64ee3e Chengchang Tang net/hns3: fix stats flip overflow > 7f2a320df9 Huisong Li net/hns3: fix query order of link status and link info > 00984de533 Viacheslav Ovsiienko net/mlx5: fix Tx queue size created with DevX > . ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [dpdk-stable] please help backporting some patches to stable release 20.11.1 2021-02-05 11:53 ` [dpdk-stable] please help backporting some patches to stable release 20.11.1 luca.boccassi 2021-02-09 10:39 ` luca.boccassi @ 2021-02-19 8:59 ` Ferruh Yigit 2021-02-22 12:00 ` Luca Boccassi 1 sibling, 1 reply; 11+ messages in thread From: Ferruh Yigit @ 2021-02-19 8:59 UTC (permalink / raw) To: dpdk stable, luca.boccassi; +Cc: Qi Zhang On 2/5/2021 11:53 AM, 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 2021/02/19. > > > 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 > > --- > c86e930165 Lance Richardson net/bnxt: fix fallback mbuf allocation logic > d5be7f9375 Qi Zhang net/ice/base: update add scheduler node counter > Hi Luca, Qi confirmed that a backport is not needed for the above ice driver, it can be skipped. Possibly there will be a patch to stable tree for it, but it is not needed now. Thanks. ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [dpdk-stable] please help backporting some patches to stable release 20.11.1 2021-02-19 8:59 ` Ferruh Yigit @ 2021-02-22 12:00 ` Luca Boccassi 0 siblings, 0 replies; 11+ messages in thread From: Luca Boccassi @ 2021-02-22 12:00 UTC (permalink / raw) To: Ferruh Yigit, dpdk stable; +Cc: Qi Zhang On Fri, 2021-02-19 at 08:59 +0000, Ferruh Yigit wrote: > On 2/5/2021 11:53 AM, 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 2021/02/19. > > > > > > 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 > > > > --- > > c86e930165 Lance Richardson net/bnxt: fix fallback mbuf allocation logic > > d5be7f9375 Qi Zhang net/ice/base: update add scheduler node counter > > > > Hi Luca, > > Qi confirmed that a backport is not needed for the above ice driver, it can be > skipped. > > Possibly there will be a patch to stable tree for it, but it is not needed now. Great, thanks for confirming. -- Kind regards, Luca Boccassi ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2021-02-22 12:00 UTC | newest] Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <20210205115222.1287558-1-luca.boccassi@gmail.com> 2021-02-05 11:53 ` [dpdk-stable] please help backporting some patches to stable release 20.11.1 luca.boccassi 2021-02-09 10:39 ` luca.boccassi 2021-02-12 23:42 ` luca.boccassi [not found] ` <20210212234341.256656-1-luca.boccassi@gmail.com> 2021-02-16 13:08 ` Wang, Haiyue 2021-02-16 13:22 ` Luca Boccassi 2021-02-18 9:41 ` Luca Boccassi 2021-02-18 13:33 ` Xueming(Steven) Li 2021-02-18 17:42 ` Luca Boccassi [not found] ` <20210209103924.468111-1-luca.boccassi@gmail.com> 2021-02-20 6:49 ` Huisong Li 2021-02-19 8:59 ` Ferruh Yigit 2021-02-22 12:00 ` Luca Boccassi
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).