please help backporting some patches to stable release 21.11.1

please help backporting some patches to stable release 21.11.1

[Kevin Traynor]

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@dpdk.org" but not "dev@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

Re: please help backporting some patches to stable release 21.11.1

[Kevin Traynor]

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@dpdk.org" but not "dev@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
> 

Re: please help backporting some patches to stable release 21.11.1

[David Marchand]

On Tue, Mar 8, 2022 at 3:51 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>
> Reminder of patches that need author rebase for 21.11.1 :-)
> > 315d14d705  Gowrishankar Muthukrishnan event/cnxk: fix memory leaks

The Fixes: tag looks wrong to me.
This fix should be pointing at 8bdbae66b299 ("event/cnxk: add external
clock support for timer").
Hence it is irrelevant to 21.11.


-- 
David Marchand

Re: please help backporting some patches to stable release 21.11.1

[Kevin Traynor]

On 10/03/2022 13:22, David Marchand wrote:
> On Tue, Mar 8, 2022 at 3:51 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>>
>> Reminder of patches that need author rebase for 21.11.1 :-)
>>> 315d14d705  Gowrishankar Muthukrishnan event/cnxk: fix memory leaks
> 
> The Fixes: tag looks wrong to me.
> This fix should be pointing at 8bdbae66b299 ("event/cnxk: add external
> clock support for timer").
> Hence it is irrelevant to 21.11.
> 
> 

ok, thanks David. I will remove from failed list for 21.11.

RE: [EXT] Re: please help backporting some patches to stable release 21.11.1

[Gowrishankar Muthukrishnan]

Ack. Thanks David for a cross check.

Regards,
Gowrishankar

> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Thursday, March 10, 2022 6:52 PM
> To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>; Kevin
> Traynor <ktraynor@redhat.com>; Jerin Jacob Kollanukkaran
> <jerinj@marvell.com>
> Cc: dpdk stable <stable@dpdk.org>
> Subject: [EXT] Re: please help backporting some patches to stable release
> 21.11.1
> 
> External Email
> 
> ----------------------------------------------------------------------
> On Tue, Mar 8, 2022 at 3:51 PM Kevin Traynor <ktraynor@redhat.com>
> wrote:
> >
> > Reminder of patches that need author rebase for 21.11.1 :-)
> > > 315d14d705  Gowrishankar Muthukrishnan event/cnxk: fix memory leaks
> 
> The Fixes: tag looks wrong to me.
> This fix should be pointing at 8bdbae66b299 ("event/cnxk: add external clock
> support for timer").
> Hence it is irrelevant to 21.11.
> 
> 
> --
> David Marchand

please help backporting some patches to stable release 21.11.1

[Kevin Traynor]

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 04/08/22.

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@dpdk.org" but not "dev@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
68f8a52a6b  Rakesh Kudurumalla net/cnxk: fix build with optimization

please help backporting some patches to stable release 21.11.1

[Kevin Traynor]

Hi commit authors (and maintainers),

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/23/22.

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@dpdk.org" but not "dev@dpdk.org".

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

Thanks.

Kevin

---
a501609ea6  Pablo de Lara    crypto/ipsec_mb: fix length and offset settings
837269c2e5  Pablo de Lara    crypto/ipsec_mb: fix GMAC parameters setting
68f8a52a6b  Rakesh Kudurumalla net/cnxk: fix build with optimization

please help backporting some patches to stable release 21.11.1

[Kevin Traynor]

(with fixed Subject)

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/14/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@dpdk.org" but not "dev@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
6d4f1066be  Jiawei Wang      net/mlx5: fix NIC egress flow mismatch in switchdev mode