patches for DPDK stable branches
 help / color / mirror / Atom feed
* please help backporting some patches to stable release 21.11.3
@ 2022-11-11 18:44 Kevin Traynor
  0 siblings, 0 replies; 14+ messages in thread
From: Kevin Traynor @ 2022-11-11 18:44 UTC (permalink / raw)
  To: dpdk stable
  Cc: Andrew Rybchenko, Chenbo Xia, David Marchand, Dongdong Liu,
	Hanumanth Pothula, Harman Kalra, Hernan Vargas, Huisong Li,
	Ivan Malov, Maxime Coquelin, Nithin Dabilpuram, Pavan Nikhilesh,
	Qi Zhang, Raslan Darawsheh, Shijith Thotton, Steve Yang,
	Sunil Kumar Kori, Thomas Monjalon, Wei Ling, Wenwu Ma

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 11/17/22.

You can find the a temporary work-in-progress branch of the coming 21.11.3
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

---
d4cbbee345  David Marchand   trace: fix metadata dump
5a0f64d84b  Hanumanth Pothula net/cnxk: fix configuring large Rx/Tx queues
59ceaa72d5  Harman Kalra     common/cnxk: fix part number for CN10K
6f3325bbfa  Hernan Vargas    baseband/acc100: add LDPC encoder padding function
2df5fe2023  Hernan Vargas    baseband/acc100: check AQ availability
5802f36dd4  Hernan Vargas    baseband/acc100: enforce additional check on FCW
75114f78cf  Hernan Vargas    baseband/acc100: fix null HARQ input case
c24d53b4cc  Hernan Vargas    baseband/acc100: fix ring availability calculation
e23491fc2e  Hernan Vargas    baseband/acc100: fix ring/queue allocation
a35799625e  Huisong Li       net/hns3: fix lock protection of RSS flow rule
1042ed401f  Huisong Li       net/hns3: fix restore filter function input
0d81da2559  Huisong Li       net/hns3: fix RSS rule restore
df810d1b6e  Ivan Malov       net/bonding: fix flow flush order on close
5781638519  Nithin Dabilpuram common/cnxk: fix RQ mask config for CN10KB chip
3fe71706ab  Pavan Nikhilesh  event/cnxk: fix stale data in workslot
927cb43fe9  Pavan Nikhilesh  examples/l3fwd: fix port group mask with AltiVec
0b241667cc  Steve Yang       net/iavf: fix tainted scalar
133c67cfd7  Thomas Monjalon  doc: add Rx buffer split capability for mlx5
40abb903fe  Wenwu Ma         examples/vhost: fix use after free


^ permalink raw reply	[flat|nested] 14+ messages in thread
* please help backporting some patches to stable release 21.11.3
@ 2022-11-30 10:02 Kevin Traynor
  0 siblings, 0 replies; 14+ messages in thread
From: Kevin Traynor @ 2022-11-30 10:02 UTC (permalink / raw)
  To: dpdk stable
  Cc: Cristian Dumitrescu, Hanumanth Pothula, Harman Kalra,
	Maxime Coquelin, Nicolas Chautru, Nithin Dabilpuram,
	Pavan Nikhilesh, Qi Zhang, Shijith Thotton, Steve Yang,
	Yogesh Jangra

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 12/02/22. After that validation will be
beginning and they will not be considered for backport until 21.11.4.

You can find the a temporary work-in-progress branch of the coming 21.11.3
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

---
5a0f64d84b  Hanumanth Pothula net/cnxk: fix configuring large Rx/Tx queues
59ceaa72d5  Harman Kalra     common/cnxk: fix part number for CN10K
e77d682aad  Nicolas Chautru  baseband/acc100: fix input error related to padding
5781638519  Nithin Dabilpuram common/cnxk: fix RQ mask config for CN10KB chip
3fe71706ab  Pavan Nikhilesh  event/cnxk: fix stale data in workslot
927cb43fe9  Pavan Nikhilesh  examples/l3fwd: fix port group mask with AltiVec
0f044b6681  Steve Yang       net/iavf: fix refine protocol header
0b241667cc  Steve Yang       net/iavf: fix tainted scalar
b125c0e721  Steve Yang       net/iavf: fix tainted scalar
a774cba0bb  Yogesh Jangra    pipeline: fix validate header instruction


^ permalink raw reply	[flat|nested] 14+ messages in thread
* please help backporting some patches to stable release 21.11.3
@ 2022-11-23 18:06 Kevin Traynor
  2022-11-24  8:01 ` Michael Baum
                   ` (4 more replies)
  0 siblings, 5 replies; 14+ messages in thread
From: Kevin Traynor @ 2022-11-23 18:06 UTC (permalink / raw)
  To: dpdk stable
  Cc: Ciara Power, Cristian Dumitrescu, David Marchand, Dongdong Liu,
	Hanumanth Pothula, Harman Kalra, Huisong Li, Jiawei Wang, Kai Ji,
	Matan Azrad, Maxime Coquelin, Michael Baum, Nicolas Chautru,
	Nithin Dabilpuram, Pavan Nikhilesh, Qi Zhang, Shijith Thotton,
	Shun Hao, Spike Du, Stephen Hemminger, Steve Yang,
	Sunil Kumar Kori, Viacheslav Ovsiienko, Yiding Zhou,
	Yogesh Jangra

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 11/29/22.

You can find the a temporary work-in-progress branch of the coming 21.11.3
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

---
d4cbbee345  David Marchand   trace: fix metadata dump
5a0f64d84b  Hanumanth Pothula net/cnxk: fix configuring large Rx/Tx queues
59ceaa72d5  Harman Kalra     common/cnxk: fix part number for CN10K
b4924c0db5  Huisong Li       net/bonding: fix mbuf fast free handling
a35799625e  Huisong Li       net/hns3: fix lock protection of RSS flow rule
1042ed401f  Huisong Li       net/hns3: fix restore filter function input
0d81da2559  Huisong Li       net/hns3: fix RSS rule restore
3e13a6ae95  Jiawei Wang      net/mlx5: fix mirror flow validation with ASO action
e9de8f33ca  Jiawei Wang      net/mlx5: fix source port checking in sample flow rule
16d6ebb65d  Kai Ji           crypto/ipsec_mb: fix null checks
ef4ece4dbb  Michael Baum     net/mlx5: fix port closing
13c5c09390  Michael Baum     net/mlx5: fix port event cleaning order
a94e89e47b  Michael Baum     net/mlx5: fix race condition in counter pool resizing
e77d682aad  Nicolas Chautru  baseband/acc100: fix input error related to padding
5781638519  Nithin Dabilpuram common/cnxk: fix RQ mask config for CN10KB chip
3fe71706ab  Pavan Nikhilesh  event/cnxk: fix stale data in workslot
927cb43fe9  Pavan Nikhilesh  examples/l3fwd: fix port group mask with AltiVec
afb98009a0  Shun Hao         net/mlx5: fix assert when creating meter policy
3b6d78bb8e  Shun Hao         net/mlx5: fix meter policy with port ID destination
0f3ba0d4a8  Spike Du         net/mlx5: fix testpmd quit with available desc threshold
21dc24b746  Stephen Hemminger ring: remove leftover comment about watermark
0f044b6681  Steve Yang       net/iavf: fix refine protocol header
0b241667cc  Steve Yang       net/iavf: fix tainted scalar
b125c0e721  Steve Yang       net/iavf: fix tainted scalar
cb5c1b91f7  Yiding Zhou      net/iavf: add thread for event callbacks
a774cba0bb  Yogesh Jangra    pipeline: fix validate header instruction


^ permalink raw reply	[flat|nested] 14+ messages in thread
* please help backporting some patches to stable release 21.11.3
@ 2022-10-25 15:35 Kevin Traynor
  0 siblings, 0 replies; 14+ messages in thread
From: Kevin Traynor @ 2022-10-25 15:35 UTC (permalink / raw)
  To: dpdk stable
  Cc: Abdullah Sevincer, Ajit Khaparde, Chenbo Xia, David Marchand,
	Dongdong Liu, Erik Gabriel Carrillo, Gagandeep Singh,
	Hanumanth Pothula, Harman Kalra, Harry van Haaren,
	Hemant Agrawal, Huisong Li, Kevin Liu, Mao YingMing,
	Pavan Nikhilesh, Qiming Yang, Qi Zhang, Somnath Kotur,
	Sunil Kumar Kori, Wei Ling, Wenwu Ma

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 11/01/22.

You can find the a temporary work-in-progress branch of the coming 21.11.3
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

---
9c9e72326b  Abdullah Sevincer event/dlb2: handle enqueuing more than maximum depth
d4cbbee345  David Marchand   trace: fix metadata dump
329280c53e  Erik Gabriel Carrillo service: fix early move to inactive status
b0074a7ba1  Gagandeep Singh  net/dpaa2: fix buffer freeing on SG Tx
8716c0ec06  Gagandeep Singh  net/dpaa: fix buffer freeing on SG Tx
5a0f64d84b  Hanumanth Pothula net/cnxk: fix configuring large Rx/Tx queues
59ceaa72d5  Harman Kalra     common/cnxk: fix part number for CN10K
1042ed401f  Huisong Li       net/hns3: fix restore filter function input
0d81da2559  Huisong Li       net/hns3: fix RSS rule restore
4bfb499829  Mao YingMing     net/bnxt: fix null pointer dereference in LED config
3fe71706ab  Pavan Nikhilesh  event/cnxk: fix stale data in workslot
b0472e210f  Qi Zhang         net/ice/base: fix input set of GTPoGRE
40abb903fe  Wenwu Ma         examples/vhost: fix use after free


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

end of thread, other threads:[~2022-12-09  6:06 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-11 18:44 please help backporting some patches to stable release 21.11.3 Kevin Traynor
  -- strict thread matches above, loose matches on Subject: below --
2022-11-30 10:02 Kevin Traynor
2022-11-23 18:06 Kevin Traynor
2022-11-24  8:01 ` Michael Baum
2022-11-24 17:02 ` Ji, Kai
2022-11-29 12:55   ` Kevin Traynor
2022-11-28  9:24 ` Spike Du
2022-11-29 12:59   ` Kevin Traynor
2022-11-28  9:28 ` Shun Hao
2022-11-29 13:06   ` Kevin Traynor
2022-11-30  8:18 ` lihuisong (C)
2022-11-30  9:51   ` Kevin Traynor
2022-12-09  6:06     ` Jiang, YuX
2022-10-25 15:35 Kevin Traynor

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).