From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: Alexander Kozyrev <akozyrev@nvidia.com>,
Chengwen Feng <fengchengwen@huawei.com>,
Ciara Power <ciara.power@intel.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Gagandeep Singh <g.singh@nxp.com>, Gavin Hu <gavin.hu@arm.com>,
Geoff Thorpe <geoff.thorpe@nxp.com>,
Gregory Etelson <getelson@nvidia.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
Jerin Jacob <jerinj@marvell.com>,
Jian Wang <jianwang@trustnetic.com>,
Jiawen Wu <jiawenwu@trustnetic.com>,
Keith Wiles <keith.wiles@intel.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
Maayan Kashani <mkashani@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Michael Baum <michaelba@nvidia.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Ola Liljedahl <ola.liljedahl@arm.com>,
Phil Yang <phil.yang@arm.com>, Rongwei Liu <rongweil@nvidia.com>,
Roy Pledge <roy.pledge@nxp.com>,
Ruifeng Wang <ruifeng.wang@arm.com>,
Sachin Saxena <sachin.saxena@nxp.com>,
Satha Rao <skoteshwar@marvell.com>,
Satheesh Paul <psatheesh@marvell.com>,
Shreyansh Jain <shreyansh.jain@nxp.com>,
Steve Capper <steve.capper@arm.com>,
Sunil Kumar Kori <skori@marvell.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Wathsala Vithanage <wathsala.vithanage@arm.com>,
Xueming Li <xuemingl@nvidia.com>
Subject: please help backporting some patches to stable release 22.11.11
Date: Wed, 12 Nov 2025 16:57:12 +0000 [thread overview]
Message-ID: <20251112165714.1618739-1-luca.boccassi@gmail.com> (raw)
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 2025/11/19.
You can find the a temporary work-in-progress branch of the coming 22.11.11
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
---
0e3c389b9e Gagandeep Singh bus/dpaa: do proper cleanup of frame queues on shutdown
d524b58819 Gregory Etelson net/mlx5: fix external queues access
6280a30607 Jiawen Wu net/ngbe: fix checksum error counter
b9ad8a6e72 Jiawen Wu net/txgbe: fix checksum error counter
17082f45e9 Maayan Kashani net/mlx5: fix modify field action restriction
112facb17b Rongwei Liu net/mlx5: fix meter mark allocation
3eec7a797f Rongwei Liu net/mlx5: remove counter alignment
d762a8fbbd Satheesh Paul net/cnxk: fix port ID default action
3bf9f0f9f0 Viacheslav Ovsiienko net/mlx5: fix control flow leakage for external SQ
8357af1cb3 Wathsala Vithanage mcslock: fix memory ordering
66d5f96278 Wathsala Vithanage ring: establish safe partial order in HTS mode
36b69b5f95 Wathsala Vithanage ring: establish safe partial order in RTS mode
next reply other threads:[~2025-11-12 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 16:57 luca.boccassi [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-27 16:24 luca.boccassi
2025-10-28 10:50 ` Nicolau, Radu
2025-10-29 10:56 ` Loftus, Ciara
2025-10-31 13:48 ` Kevin Traynor
2025-11-03 10:20 ` Loftus, Ciara
2025-11-03 10:25 ` Kevin Traynor
2025-10-29 14:29 ` David Marchand
2025-11-02 9:43 ` Gregory Etelson
2025-11-12 11:52 ` Slava Ovsiienko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251112165714.1618739-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=akozyrev@nvidia.com \
--cc=ciara.power@intel.com \
--cc=dsosnowski@nvidia.com \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@intel.com \
--cc=g.singh@nxp.com \
--cc=gavin.hu@arm.com \
--cc=geoff.thorpe@nxp.com \
--cc=getelson@nvidia.com \
--cc=hemant.agrawal@nxp.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=jianwang@trustnetic.com \
--cc=jiawenwu@trustnetic.com \
--cc=keith.wiles@intel.com \
--cc=kirankumark@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=ndabilpuram@marvell.com \
--cc=ola.liljedahl@arm.com \
--cc=phil.yang@arm.com \
--cc=psatheesh@marvell.com \
--cc=rongweil@nvidia.com \
--cc=roy.pledge@nxp.com \
--cc=ruifeng.wang@arm.com \
--cc=sachin.saxena@nxp.com \
--cc=shreyansh.jain@nxp.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=stable@dpdk.org \
--cc=steve.capper@arm.com \
--cc=viacheslavo@nvidia.com \
--cc=wathsala.vithanage@arm.com \
--cc=xuemingl@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).