* please help backporting some patches to stable release 22.11.5
@ 2024-03-14 0:17 luca.boccassi
0 siblings, 0 replies; 6+ messages in thread
From: luca.boccassi @ 2024-03-14 0:17 UTC (permalink / raw)
To: dpdk stable
Cc: Alex Vesker, Bing Zhao, Dariusz Sosnowski, Erez Shitrit,
Itamar Gozlan, Kiran Kumar K, Matan Azrad, Nithin Dabilpuram,
Ori Kam, Pavan Nikhilesh, Rahul Bhansali, Satha Rao,
Sunil Kumar Kori, Viacheslav Ovsiienko, Xiaoyu Min
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 03/21/24.
You can find the a temporary work-in-progress branch of the coming 22.11.5
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 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.
Luca Boccassi
---
d755221b77 Dariusz Sosnowski net/mlx5: fix flow counter cache starvation
e23edbc509 Itamar Gozlan net/mlx5/hws: skip item when inserting rules by index
3232c95d2c Nithin Dabilpuram net/cnxk: fix indirect mbuf handling in Tx
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: please help backporting some patches to stable release 22.11.5
2024-03-28 17:27 luca.boccassi
@ 2024-03-28 17:31 ` Gregory Etelson
0 siblings, 0 replies; 6+ messages in thread
From: Gregory Etelson @ 2024-03-28 17:31 UTC (permalink / raw)
To: dpdk stable; +Cc: NBU-Contact-Thomas Monjalon (EXTERNAL)
[-- Attachment #1: Type: text/plain, Size: 3208 bytes --]
Hello Luca,
The following patches do not need to be backported:
4359d9d1f7 Gregory Etelson net/mlx5: fix sync meter processing in HWS
dc7faa1351 Gregory Etelson net/mlx5: fix sync flow meter action
Regards,
Gregory
________________________________
From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
Sent: Thursday, March 28, 2024 19:27
To: dpdk stable <stable@dpdk.org>
Cc: NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>; Nithin Dabilpuram <ndabilpuram@marvell.com>; Itamar Gozlan <igozlan@nvidia.com>; Stephen Hemminger <stephen@networkplumber.org>; Kumara Parameshwaran <kumaraparamesh92@gmail.com>; Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>; Gregory Etelson <getelson@nvidia.com>; Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: please help backporting some patches to stable release 22.11.5
External email: Use caution opening links or attachments
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 2024/04/03.
You can find the a temporary work-in-progress branch of the coming 22.11.5
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 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.
Luca Boccassi
---
df33fb53e4 Honnappa Nagarahalli rcu: fix acked token in debug log
063cddfc74 Honnappa Nagarahalli rcu: use atomic operation on acked token
547f294357 Kumara Parameshwaran gro: fix reordering of packets
323b626a86 Stephen Hemminger net/sfc: fix compile-time check
e23edbc509 Itamar Gozlan net/mlx5/hws: skip item when inserting rules by index
3232c95d2c Nithin Dabilpuram net/cnxk: fix indirect mbuf handling in Tx
5ecc8df4fa Dariusz Sosnowski net/mlx5: fix async flow create error handling
ff9433b578 Dariusz Sosnowski net/mlx5: fix flow configure validation
727283742a Dariusz Sosnowski net/mlx5: fix rollback on failed flow configure
4359d9d1f7 Gregory Etelson net/mlx5: fix sync meter processing in HWS
dc7faa1351 Gregory Etelson net/mlx5: fix sync flow meter action
[-- Attachment #2: Type: text/html, Size: 5636 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* please help backporting some patches to stable release 22.11.5
@ 2024-03-28 17:27 luca.boccassi
2024-03-28 17:31 ` Gregory Etelson
0 siblings, 1 reply; 6+ messages in thread
From: luca.boccassi @ 2024-03-28 17:27 UTC (permalink / raw)
To: dpdk stable
Cc: Thomas Monjalon, Nithin Dabilpuram, Itamar Gozlan,
Stephen Hemminger, Kumara Parameshwaran, Honnappa Nagarahalli,
Gregory Etelson, Dariusz Sosnowski
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 2024/04/03.
You can find the a temporary work-in-progress branch of the coming 22.11.5
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 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.
Luca Boccassi
---
df33fb53e4 Honnappa Nagarahalli rcu: fix acked token in debug log
063cddfc74 Honnappa Nagarahalli rcu: use atomic operation on acked token
547f294357 Kumara Parameshwaran gro: fix reordering of packets
323b626a86 Stephen Hemminger net/sfc: fix compile-time check
e23edbc509 Itamar Gozlan net/mlx5/hws: skip item when inserting rules by index
3232c95d2c Nithin Dabilpuram net/cnxk: fix indirect mbuf handling in Tx
5ecc8df4fa Dariusz Sosnowski net/mlx5: fix async flow create error handling
ff9433b578 Dariusz Sosnowski net/mlx5: fix flow configure validation
727283742a Dariusz Sosnowski net/mlx5: fix rollback on failed flow configure
4359d9d1f7 Gregory Etelson net/mlx5: fix sync meter processing in HWS
dc7faa1351 Gregory Etelson net/mlx5: fix sync flow meter action
^ permalink raw reply [flat|nested] 6+ messages in thread
* please help backporting some patches to stable release 22.11.5
@ 2024-03-25 12:18 luca.boccassi
0 siblings, 0 replies; 6+ messages in thread
From: luca.boccassi @ 2024-03-25 12:18 UTC (permalink / raw)
To: dpdk stable
Cc: Dariusz Sosnowski, Gregory Etelson, Matan Azrad, Viacheslav Ovsiienko
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 04/01/24.
You can find the a temporary work-in-progress branch of the coming 22.11.5
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 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.
Luca Boccassi
---
dc7faa1351 Gregory Etelson net/mlx5: fix sync flow meter action
^ permalink raw reply [flat|nested] 6+ messages in thread
* please help backporting some patches to stable release 22.11.5
@ 2024-03-18 15:41 luca.boccassi
0 siblings, 0 replies; 6+ messages in thread
From: luca.boccassi @ 2024-03-18 15:41 UTC (permalink / raw)
To: dpdk stable
Cc: Alexander Kozyrev, Bing Zhao, Dariusz Sosnowski, Gregory Etelson,
Matan Azrad, Michael Baum, Ori Kam, Suanming Mou,
Viacheslav Ovsiienko, Thomas Monjalon
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 03/25/24.
You can find the a temporary work-in-progress branch of the coming 22.11.5
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 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.
Luca Boccassi
---
5ecc8df4fa Dariusz Sosnowski net/mlx5: fix async flow create error handling
ff9433b578 Dariusz Sosnowski net/mlx5: fix flow configure validation
727283742a Dariusz Sosnowski net/mlx5: fix rollback on failed flow configure
4359d9d1f7 Gregory Etelson net/mlx5: fix sync meter processing in HWS
^ permalink raw reply [flat|nested] 6+ messages in thread
* please help backporting some patches to stable release 22.11.5
@ 2024-03-07 1:38 luca.boccassi
0 siblings, 0 replies; 6+ messages in thread
From: luca.boccassi @ 2024-03-07 1:38 UTC (permalink / raw)
To: dpdk stable
Cc: Anatoly Burakov, Andrew Rybchenko, Chaoyong He, Chenbo Xia,
David Marchand, Eelco Chaudron, Gavin Hu, Heinrich Kuhn,
Honnappa Nagarahalli, Ivan Malov, Jianfeng Tan, Jiayu Hu,
Jiayu Hu, Kumara Parameshwaran, Long Wu, Maxime Coquelin,
Nathan Brown, Niklas Söderlund, Ola Liljedahl, Peng Zhang,
Ruifeng Wang, Simon Horman, Stephen Hemminger, Tiwei Bie,
Tyler Retzlaff
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 03/14/24.
You can find the a temporary work-in-progress branch of the coming 22.11.5
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 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.
Luca Boccassi
---
8b8f116b19 Chaoyong He net/nfp: fix resource leak for CoreNIC firmware
66d5f53d3e Chaoyong He net/nfp: fix resource leak for exit of CoreNIC firmware
a256a1227d Chaoyong He net/nfp: fix resource leak for exit of flower firmware
7c596721ae Chaoyong He net/nfp: fix resource leak for flower firmware
b3e42d9236 David Marchand vhost: fix virtqueue access check in vhost-user setup
df33fb53e4 Honnappa Nagarahalli rcu: fix acked token in debug log
063cddfc74 Honnappa Nagarahalli rcu: use atomic operation on acked token
547f294357 Kumara Parameshwaran gro: fix reordering of packets
243bbfa0f9 Long Wu net/nfp: fix device close
09309f8735 Long Wu net/nfp: fix device resource freeing
20eaa8e2eb Long Wu net/nfp: free switch domain ID on close
323b626a86 Stephen Hemminger net/sfc: fix compile-time check
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2024-03-28 17:31 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-14 0:17 please help backporting some patches to stable release 22.11.5 luca.boccassi
-- strict thread matches above, loose matches on Subject: below --
2024-03-28 17:27 luca.boccassi
2024-03-28 17:31 ` Gregory Etelson
2024-03-25 12:18 luca.boccassi
2024-03-18 15:41 luca.boccassi
2024-03-07 1:38 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).