Re: please help backporting some patches to stable release 22.11.3

Re: please help backporting some patches to stable release 22.11.3

[huangdengdui]

Hi,
The "db42a84233  Dengdui Huang    app/testpmd: fix crash with invalid queue"
no need to backport, because this patch depend on a new API in 23.07,
in addition, this bug has little impact.

On 2023/6/19 10:24, Xueming Li 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 22.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 22.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 07/16/23.
> 
> You can find the a temporary work-in-progress branch of the coming 22.11.3
> release at:
>     https://git.dpdk.org/dpdk-stable/log/?h=22.11-staging
> 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 22.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 22.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 22.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Xueming Li <xuemingl@nvidia.com>
> 
> ---
> 925c27ec8d  Chaoyong He      net/nfp: fix offloading flows
> e97738919c  Chaoyong He      net/nfp: fix Tx descriptor free logic of NFD3
> db42a84233  Dengdui Huang    app/testpmd: fix crash with invalid queue
> cd41a27154  Jie Hai          net/hns3: get FEC capability from firmware
> 772e30281a  Rahul Bhansali   common/cnxk: fix CPT backpressure disable on LBK
> b37fe88a2c  Srujana Challa   event/cnxk: fix LMTST write for single event mode
> a37335bc62  Viacheslav Ovsiienko eal: choose IOVA mode according to compilation option

Re: please help backporting some patches to stable release 22.11.3

[Xueming(Steven) Li]

[-- Attachment #1: Type: text/plain, Size: 2692 bytes --]

Ack

Thanks for confirmation!
________________________________
From: huangdengdui <huangdengdui@huawei.com>
Sent: Tuesday, June 20, 2023 9:40 AM
To: dpdk stable <stable@dpdk.org>; Xueming(Steven) Li <xuemingl@nvidia.com>
Subject: Re: please help backporting some patches to stable release 22.11.3

Hi,
The "db42a84233  Dengdui Huang    app/testpmd: fix crash with invalid queue"
no need to backport, because this patch depend on a new API in 23.07,
in addition, this bug has little impact.

On 2023/6/19 10:24, Xueming Li 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 22.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 22.11 branch, or
>     - Indicate that the patch should not be backported
>
> Please do either of the above by 07/16/23.
>
> You can find the a temporary work-in-progress branch of the coming 22.11.3
> release at:
>     https://git.dpdk.org/dpdk-stable/log/?h=22.11-staging
> 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 22.11] foo/bar: fix baz
>
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 22.11'
>
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>
> FYI, branch 22.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
>
> Thanks.
>
> Xueming Li <xuemingl@nvidia.com>
>
> ---
> 925c27ec8d  Chaoyong He      net/nfp: fix offloading flows
> e97738919c  Chaoyong He      net/nfp: fix Tx descriptor free logic of NFD3
> db42a84233  Dengdui Huang    app/testpmd: fix crash with invalid queue
> cd41a27154  Jie Hai          net/hns3: get FEC capability from firmware
> 772e30281a  Rahul Bhansali   common/cnxk: fix CPT backpressure disable on LBK
> b37fe88a2c  Srujana Challa   event/cnxk: fix LMTST write for single event mode
> a37335bc62  Viacheslav Ovsiienko eal: choose IOVA mode according to compilation option

[-- Attachment #2: Type: text/html, Size: 4710 bytes --]

RE: please help backporting some patches to stable release 22.11.3

[Xueming(Steven) Li]

Hi Kishore,

Thanks for the confirmation!

If no "Cc: stable@dpdk.org" in original patch, the scanning scripts will ignore the patch.

Regards,
Xueming Li

> -----Original Message-----
> From: Kishore Padmanabha <kishore.padmanabha@broadcom.com>
> Sent: 8/11/2023 22:25
> To: dpdk stable <stable@dpdk.org>
> Cc: Luca Boccassi <bluca@debian.org>; Ajit Kumar Khaparde
> <ajit.khaparde@broadcom.com>; Ankur Dwivedi <adwivedi@marvell.com>;
> Anoob Joseph <anoobj@marvell.com>; Dan Nowlin <dan.nowlin@intel.com>;
> Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>; Harman Kalra
> <hkalra@marvell.com>; Jerin Jacob <jerinj@marvell.com>; Kiran Kumar K
> <kirankumark@marvell.com>; Leyi Rong <leyi.rong@intel.com>; Michael
> Baucom <michael.baucom@broadcom.com>; Mingjin Ye
> <mingjinx.ye@intel.com>; Nithin Dabilpuram <ndabilpuram@marvell.com>;
> Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>; Qiming Yang
> <qiming.yang@intel.com>; Qi Zhang <qi.z.zhang@intel.com>; Randy Schacher
> <stuart.schacher@broadcom.com>; Satha Rao <skoteshwar@marvell.com>;
> Shahaji Bhosle <sbhosle@broadcom.com>; Somnath Kotur
> <somnath.kotur@broadcom.com>; Sunil Kumar Kori <skori@marvell.com>;
> Tejasree Kondoj <ktejasree@marvell.com>; Venkat Duvvuru
> <venkatkumar.duvvuru@broadcom.com>
> Subject: RE: please help backporting some patches to stable release 22.11.3
> 
> Hi Xueming,
> 
> The patch "8c047e823a  Kishore Padmanabha net/bnxt: fix multi-root card
> support" is not required for 22.11 release. This need not be backported to
> older branch.
> 
> Thanks,
> Kishore
> 
> -----Original Message-----
> From: Xueming Li <xuemingl@nvidia.com>
> Sent: Wednesday, August 9, 2023 8:07 PM
> Cc: dpdk stable <stable@dpdk.org>; Luca Boccassi <bluca@debian.org>; Ajit
> Khaparde <ajit.khaparde@broadcom.com>; Ankur Dwivedi
> <adwivedi@marvell.com>; Anoob Joseph <anoobj@marvell.com>; Dan
> Nowlin
> <dan.nowlin@intel.com>; Gowrishankar Muthukrishnan
> <gmuthukrishn@marvell.com>; Harman Kalra <hkalra@marvell.com>; Jerin
> Jacob
> <jerinj@marvell.com>; Kiran Kumar K <kirankumark@marvell.com>; Kishore
> Padmanabha <kishore.padmanabha@broadcom.com>; Leyi Rong
> <leyi.rong@intel.com>; Mike Baucom <michael.baucom@broadcom.com>;
> Mingjin
> Ye <mingjinx.ye@intel.com>; Nithin Dabilpuram
> <ndabilpuram@marvell.com>;
> Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>; Qiming Yang
> <qiming.yang@intel.com>; Qi Zhang <qi.z.zhang@intel.com>; Randy Schacher
> <stuart.schacher@broadcom.com>; Satha Rao <skoteshwar@marvell.com>;
> Shahaji Bhosle <sbhosle@broadcom.com>; Somnath Kotur
> <somnath.kotur@broadcom.com>; Sunil Kumar Kori <skori@marvell.com>;
> Tejasree Kondoj <ktejasree@marvell.com>; Venkat Duvvuru
> <venkatkumar.duvvuru@broadcom.com>
> Subject: please help backporting some patches to stable release 22.11.3
> 
> 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 22.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 22.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 08/16/23.
> 
> You can find the a temporary work-in-progress branch of the coming 22.11.3
> release at:
>     https://git.dpdk.org/dpdk-stable/log/?h=22.11-staging
> 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=d90e6ae6f936ecdc2fd381
> 1ff9f26aec7f3c06eb
> 
> When sending the backported patch, please indicate the target branch in
> the subject line, as we have multiple branches, for example:
>     [PATCH 22.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 22.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 22.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Xueming Li <xuemingl@nvidia.com>
> 
> ---
> 3885644d91  Gowrishankar Muthukrishnan crypto/cnxk: fix order of ECFPM
> parameters
> 1c7a4d37e7  Harman Kalra     common/cnxk: fix mailbox timeout due to
> deadlock
> 8c047e823a  Kishore Padmanabha net/bnxt: fix multi-root card support
> 6fd3a7a618  Mingjin Ye       net/ice/base: fix internal etype in switch
> filter
> 
> --
> This electronic communication and the information and any files transmitted
> with it, or attached to it, are confidential and are intended solely for
> the use of the individual or entity to whom it is addressed and may contain
> information that is confidential, legally privileged, protected by privacy
> laws, or otherwise restricted from disclosure to anyone else. If you are
> not the intended recipient or the person responsible for delivering the
> e-mail to the intended recipient, you are hereby notified that any use,
> copying, distributing, dissemination, forwarding, printing, or copying of
> this e-mail is strictly prohibited. If you received this e-mail in error,
> please return the e-mail to the sender, delete it from your computer, and
> destroy any printed copy of it.

RE: please help backporting some patches to stable release 22.11.3

[Kishore Padmanabha]

[-- Attachment #1: Type: text/plain, Size: 3966 bytes --]

Hi Xueming,

The patch "8c047e823a  Kishore Padmanabha net/bnxt: fix multi-root card
support" is not required for 22.11 release. This need not be backported to
older branch.

Thanks,
Kishore

-----Original Message-----
From: Xueming Li <xuemingl@nvidia.com>
Sent: Wednesday, August 9, 2023 8:07 PM
Cc: dpdk stable <stable@dpdk.org>; Luca Boccassi <bluca@debian.org>; Ajit
Khaparde <ajit.khaparde@broadcom.com>; Ankur Dwivedi
<adwivedi@marvell.com>; Anoob Joseph <anoobj@marvell.com>; Dan Nowlin
<dan.nowlin@intel.com>; Gowrishankar Muthukrishnan
<gmuthukrishn@marvell.com>; Harman Kalra <hkalra@marvell.com>; Jerin Jacob
<jerinj@marvell.com>; Kiran Kumar K <kirankumark@marvell.com>; Kishore
Padmanabha <kishore.padmanabha@broadcom.com>; Leyi Rong
<leyi.rong@intel.com>; Mike Baucom <michael.baucom@broadcom.com>; Mingjin
Ye <mingjinx.ye@intel.com>; Nithin Dabilpuram <ndabilpuram@marvell.com>;
Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>; Qiming Yang
<qiming.yang@intel.com>; Qi Zhang <qi.z.zhang@intel.com>; Randy Schacher
<stuart.schacher@broadcom.com>; Satha Rao <skoteshwar@marvell.com>;
Shahaji Bhosle <sbhosle@broadcom.com>; Somnath Kotur
<somnath.kotur@broadcom.com>; Sunil Kumar Kori <skori@marvell.com>;
Tejasree Kondoj <ktejasree@marvell.com>; Venkat Duvvuru
<venkatkumar.duvvuru@broadcom.com>
Subject: please help backporting some patches to stable release 22.11.3

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 22.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 22.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 08/16/23.

You can find the a temporary work-in-progress branch of the coming 22.11.3
release at:
    https://git.dpdk.org/dpdk-stable/log/?h=22.11-staging
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=d90e6ae6f936ecdc2fd381
1ff9f26aec7f3c06eb

When sending the backported patch, please indicate the target branch in
the subject line, as we have multiple branches, for example:
    [PATCH 22.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 22.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 22.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Xueming Li <xuemingl@nvidia.com>

---
3885644d91  Gowrishankar Muthukrishnan crypto/cnxk: fix order of ECFPM
parameters
1c7a4d37e7  Harman Kalra     common/cnxk: fix mailbox timeout due to
deadlock
8c047e823a  Kishore Padmanabha net/bnxt: fix multi-root card support
6fd3a7a618  Mingjin Ye       net/ice/base: fix internal etype in switch
filter

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4227 bytes --]

please help backporting some patches to stable release 22.11.3

[Xueming Li]

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 22.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 22.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 08/16/23.

You can find the a temporary work-in-progress branch of the coming 22.11.3
release at:
    https://git.dpdk.org/dpdk-stable/log/?h=22.11-staging
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 22.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 22.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 22.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Xueming Li <xuemingl@nvidia.com>

---
3885644d91  Gowrishankar Muthukrishnan crypto/cnxk: fix order of ECFPM parameters
1c7a4d37e7  Harman Kalra     common/cnxk: fix mailbox timeout due to deadlock
8c047e823a  Kishore Padmanabha net/bnxt: fix multi-root card support
6fd3a7a618  Mingjin Ye       net/ice/base: fix internal etype in switch filter