patches for DPDK stable branches
 help / color / mirror / Atom feed
* please help backporting some patches to stable release 21.11.1
@ 2022-04-05 15:06 Kevin Traynor
  2022-04-06  6:31 ` [EXT] " Gowrishankar Muthukrishnan
  0 siblings, 1 reply; 9+ messages in thread
From: Kevin Traynor @ 2022-04-05 15:06 UTC (permalink / raw)
  To: dpdk stable
  Cc: Daxue Gao, Gowrishankar Muthukrishnan, Jerin Jacob, Rakesh Kudurumalla

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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* RE: [EXT] please help backporting some patches to stable release 21.11.1
  2022-04-05 15:06 please help backporting some patches to stable release 21.11.1 Kevin Traynor
@ 2022-04-06  6:31 ` Gowrishankar Muthukrishnan
  2022-04-06  9:39   ` Kevin Traynor
  0 siblings, 1 reply; 9+ messages in thread
From: Gowrishankar Muthukrishnan @ 2022-04-06  6:31 UTC (permalink / raw)
  To: Kevin Traynor
  Cc: Daxue Gao, Jerin Jacob Kollanukkaran, Rakesh Kudurumalla,
	dpdk stable, Pavan Nikhilesh Bhagavatula

Hi Kevin,
Please ignore below patch, as its correct parent patch is 8bdbae66b29 which is not
applicable for 21.11 lts.

315d14d705  Gowrishankar Muthukrishnan event/cnxk: fix memory leaks

Thanks for the heads up,
Gowrishankar

> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: Tuesday, April 5, 2022 8:36 PM
> To: dpdk stable <stable@dpdk.org>
> Cc: Daxue Gao <daxuex.gao@intel.com>; Gowrishankar Muthukrishnan
> <gmuthukrishn@marvell.com>; Jerin Jacob Kollanukkaran
> <jerinj@marvell.com>; Rakesh Kudurumalla <rkudurumalla@marvell.com>
> Subject: [EXT] please help backporting some patches to stable release
> 21.11.1
> 
> External Email
> 
> ----------------------------------------------------------------------
> 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://urldefense.proofpoint.com/v2/url?u=https-
> 3A__git.dpdk.org_dpdk-2Dstable_commit_-3Fh-3D18.11-26id-
> 3Dd90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb&d=DwIDAg&c=nKjWec2b6R
> 0mOyPaz7xtfQ&r=EAtr-
> g7yUFhtOio8r2Rtm13Aqe4WVp_S_gHpcu6KFVo&m=j0EyEihXoey-
> V3LVeQLzaLP5yIQ7UnoyOsjyugbqwqhQsqLAY2MLuJDQV1FYIrqz&s=CiXClXhR
> XUM0MWZeczFG8POC1BSsmRnnAhJqC4X4GmU&e=
> 
> 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://urldefense.proofpoint.com/v2/url?u=https-
> 3A__git.dpdk.org_dpdk-
> 2Dstable&d=DwIDAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=EAtr-
> g7yUFhtOio8r2Rtm13Aqe4WVp_S_gHpcu6KFVo&m=j0EyEihXoey-
> V3LVeQLzaLP5yIQ7UnoyOsjyugbqwqhQsqLAY2MLuJDQV1FYIrqz&s=gPt7G2A
> NGvpHDNUkA15_3PSCZ3A1VQPx3zEyUKCuApQ&e=
> 
> Thanks.
> 
> Kevin
> 
> ---
> 315d14d705  Gowrishankar Muthukrishnan event/cnxk: fix memory leaks
> 68f8a52a6b  Rakesh Kudurumalla net/cnxk: fix build with optimization


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [EXT] please help backporting some patches to stable release 21.11.1
  2022-04-06  6:31 ` [EXT] " Gowrishankar Muthukrishnan
@ 2022-04-06  9:39   ` Kevin Traynor
  0 siblings, 0 replies; 9+ messages in thread
From: Kevin Traynor @ 2022-04-06  9:39 UTC (permalink / raw)
  To: Gowrishankar Muthukrishnan
  Cc: Daxue Gao, Jerin Jacob Kollanukkaran, Rakesh Kudurumalla,
	dpdk stable, Pavan Nikhilesh Bhagavatula

On 06/04/2022 07:31, Gowrishankar Muthukrishnan wrote:
> Hi Kevin,
> Please ignore below patch, as its correct parent patch is 8bdbae66b29 which is not
> applicable for 21.11 lts.
> 
> 315d14d705  Gowrishankar Muthukrishnan event/cnxk: fix memory leaks
> 

Thanks Gowri. Removed it from the failed to apply list.

Kevin.

> Thanks for the heads up,
> Gowrishankar
> 
>> -----Original Message-----
>> From: Kevin Traynor <ktraynor@redhat.com>
>> Sent: Tuesday, April 5, 2022 8:36 PM
>> To: dpdk stable <stable@dpdk.org>
>> Cc: Daxue Gao <daxuex.gao@intel.com>; Gowrishankar Muthukrishnan
>> <gmuthukrishn@marvell.com>; Jerin Jacob Kollanukkaran
>> <jerinj@marvell.com>; Rakesh Kudurumalla <rkudurumalla@marvell.com>
>> Subject: [EXT] please help backporting some patches to stable release
>> 21.11.1
>>
>> External Email
>>
>> ----------------------------------------------------------------------
>> 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://urldefense.proofpoint.com/v2/url?u=https-
>> 3A__git.dpdk.org_dpdk-2Dstable_commit_-3Fh-3D18.11-26id-
>> 3Dd90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb&d=DwIDAg&c=nKjWec2b6R
>> 0mOyPaz7xtfQ&r=EAtr-
>> g7yUFhtOio8r2Rtm13Aqe4WVp_S_gHpcu6KFVo&m=j0EyEihXoey-
>> V3LVeQLzaLP5yIQ7UnoyOsjyugbqwqhQsqLAY2MLuJDQV1FYIrqz&s=CiXClXhR
>> XUM0MWZeczFG8POC1BSsmRnnAhJqC4X4GmU&e=
>>
>> 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://urldefense.proofpoint.com/v2/url?u=https-
>> 3A__git.dpdk.org_dpdk-
>> 2Dstable&d=DwIDAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=EAtr-
>> g7yUFhtOio8r2Rtm13Aqe4WVp_S_gHpcu6KFVo&m=j0EyEihXoey-
>> V3LVeQLzaLP5yIQ7UnoyOsjyugbqwqhQsqLAY2MLuJDQV1FYIrqz&s=gPt7G2A
>> NGvpHDNUkA15_3PSCZ3A1VQPx3zEyUKCuApQ&e=
>>
>> Thanks.
>>
>> Kevin
>>
>> ---
>> 315d14d705  Gowrishankar Muthukrishnan event/cnxk: fix memory leaks
>> 68f8a52a6b  Rakesh Kudurumalla net/cnxk: fix build with optimization
> 


^ permalink raw reply	[flat|nested] 9+ messages in thread

* please help backporting some patches to stable release 21.11.1
@ 2022-03-21 16:02 Kevin Traynor
  0 siblings, 0 replies; 9+ messages in thread
From: Kevin Traynor @ 2022-03-21 16:02 UTC (permalink / raw)
  To: dpdk stable
  Cc: Daxue Gao, Fan Zhang, Jerin Jacob, Pablo de Lara, Radu Nicolau,
	Rakesh Kudurumalla

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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: please help backporting some patches to stable release 21.11.1
  2022-03-10 13:22   ` David Marchand
@ 2022-03-10 13:27     ` Kevin Traynor
  0 siblings, 0 replies; 9+ messages in thread
From: Kevin Traynor @ 2022-03-10 13:27 UTC (permalink / raw)
  To: David Marchand, Gowrishankar Muthukrishnan, Jerin Jacob; +Cc: dpdk stable

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.


^ permalink raw reply	[flat|nested] 9+ messages in thread

* please help backporting some patches to stable release 21.11.1
@ 2022-03-10 13:23 Kevin Traynor
  0 siblings, 0 replies; 9+ messages in thread
From: Kevin Traynor @ 2022-03-10 13:23 UTC (permalink / raw)
  To: dpdk stable
  Cc: Jiawei Wang, Gowrishankar Muthukrishnan, Harman Kalra,
	Jerin Jacob, Kiran Kumar K, Nithin Dabilpuram, Pavan Nikhilesh,
	Satha Rao, Satheesh Paul, Shijith Thotton, Sunil Kumar Kori,
	Viacheslav Ovsiienko, Ori Kam

(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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: please help backporting some patches to stable release 21.11.1
  2022-03-08 14:51 ` Kevin Traynor
@ 2022-03-10 13:22   ` David Marchand
  2022-03-10 13:27     ` Kevin Traynor
  0 siblings, 1 reply; 9+ messages in thread
From: David Marchand @ 2022-03-10 13:22 UTC (permalink / raw)
  To: Gowrishankar Muthukrishnan, Kevin Traynor, Jerin Jacob; +Cc: dpdk stable

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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: please help backporting some patches to stable release 21.11.1
  2022-03-01 11:21 Kevin Traynor
@ 2022-03-08 14:51 ` Kevin Traynor
  2022-03-10 13:22   ` David Marchand
  0 siblings, 1 reply; 9+ messages in thread
From: Kevin Traynor @ 2022-03-08 14:51 UTC (permalink / raw)
  To: dpdk stable
  Cc: Chenbo Xia, Gowrishankar Muthukrishnan, Harman Kalra,
	Jerin Jacob, Kiran Kumar K, Maxime Coquelin, Nithin Dabilpuram,
	Pavan Nikhilesh, Satha Rao, Satheesh Paul, Shijith Thotton,
	Sunil Kumar Kori, Xuan Ding, Yuan Wang

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
> 


^ permalink raw reply	[flat|nested] 9+ messages in thread

* please help backporting some patches to stable release 21.11.1
@ 2022-03-01 11:21 Kevin Traynor
  2022-03-08 14:51 ` Kevin Traynor
  0 siblings, 1 reply; 9+ messages in thread
From: Kevin Traynor @ 2022-03-01 11:21 UTC (permalink / raw)
  To: dpdk stable
  Cc: Chenbo Xia, Gowrishankar Muthukrishnan, Harman Kalra,
	Jerin Jacob, Kiran Kumar K, Maxime Coquelin, Nithin Dabilpuram,
	Pavan Nikhilesh, Satha Rao, Satheesh Paul, Shijith Thotton,
	Sunil Kumar Kori, Xuan Ding, Yuan Wang

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


^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2022-04-06  9:43 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-05 15:06 please help backporting some patches to stable release 21.11.1 Kevin Traynor
2022-04-06  6:31 ` [EXT] " Gowrishankar Muthukrishnan
2022-04-06  9:39   ` Kevin Traynor
  -- strict thread matches above, loose matches on Subject: below --
2022-03-21 16:02 Kevin Traynor
2022-03-10 13:23 Kevin Traynor
2022-03-01 11:21 Kevin Traynor
2022-03-08 14:51 ` Kevin Traynor
2022-03-10 13:22   ` David Marchand
2022-03-10 13:27     ` Kevin Traynor

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ http://inbox.dpdk.org/stable \
		stable@dpdk.org
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.stable


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git