From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: "Aman Singh" <aman.deep.singh@intel.com>,
"Anatoly Burakov" <anatoly.burakov@intel.com>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
"Arkadiusz Kusztal" <arkadiuszx.kusztal@intel.com>,
"Bruce Richardson" <bruce.richardson@intel.com>,
"Chengwen Feng" <fengchengwen@huawei.com>,
"Ciara Loftus" <ciara.loftus@intel.com>,
"Cunming Liang" <cunming.liang@intel.com>,
"Dariusz Sosnowski" <dsosnowski@nvidia.com>,
"David Marchand" <david.marchand@redhat.com>,
"Dengdui Huang" <huangdengdui@huawei.com>,
"Dongdong Liu" <liudongdong3@huawei.com>,
"Ferruh Yigit" <ferruh.yigit@intel.com>,
"Gagandeep Singh" <g.singh@nxp.com>,
"Gage Eads" <gage.eads@intel.com>,
"Gregory Etelson" <getelson@nvidia.com>,
"Haiyue Wang" <haiyue.wang@intel.com>,
"Hemant Agrawal" <hemant.agrawal@nxp.com>,
"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
"Huisong Li" <lihuisong@huawei.com>,
"Jasper Tran O'Leary" <jtranoleary@google.com>,
"Jiayu Hu" <jiayu.hu@intel.com>,
"Joshua Washington" <joshwash@google.com>,
"Joyce Kong" <joyce.kong@arm.com>,
"Junfeng Guo" <junfengg@nvidia.com>,
"Jun Yang" <jun.yang@nxp.com>, "Kai Ji" <kai.ji@intel.com>,
"Keith Wiles" <keith.wiles@intel.com>,
"Khadem Ullah" <14pwcse1224@uetpeshawar.edu.pk>,
"Konstantin Ananyev" <konstantin.ananyev@huawei.com>,
"Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>,
"Kumara Parameshwaran" <kumaraparamesh92@gmail.com>,
"Leyi Rong" <leyi.rong@intel.com>,
"Lijun Ou" <oulijun@huawei.com>,
"Maayan Kashani" <mkashani@nvidia.com>,
"Matan Azrad" <matan@nvidia.com>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"Michael Baum" <michaelba@nvidia.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Nalla Pradeep" <pnalla@marvell.com>,
"Nipun Gupta" <nipun.gupta@nxp.com>,
"Olga Shern" <olgas@nvidia.com>,
"Olivier Matz" <olivier.matz@6wind.com>,
"Pascal Mazon" <pascal.mazon@6wind.com>,
"Pavan Nikhilesh" <pbhagavatula@marvell.com>,
"Prashant Gupta" <prashant.gupta_3@nxp.com>,
"Radha Mohan Chintakuntla" <radhac@marvell.com>,
"Radu Nicolau" <radu.nicolau@intel.com>,
"Raja Zidane" <rzidane@nvidia.com>,
"Robin Jarry" <rjarry@redhat.com>,
"Rongwei Liu" <rongweil@nvidia.com>,
"Sachin Saxena" <sachin.saxena@nxp.com>,
"Sameh Gobriel" <sameh.gobriel@intel.com>,
"Sathesh Edara" <sedara@marvell.com>,
"Shreyansh Jain" <shreyansh.jain@nxp.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Tathagat Priyadarshi" <tathagat.dpdk@gmail.com>,
"Vamsi Attunuru" <vattunuru@marvell.com>,
"Veerasenareddy Burru" <vburru@marvell.com>,
"Viacheslav Ovsiienko" <viacheslavo@nvidia.com>,
"Vladimir Medvedkin" <vladimir.medvedkin@intel.com>,
"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
"Wenzhuo Lu" <wenzhuo.lu@intel.com>,
"Xiaoyun Li" <xiaoyun.li@intel.com>,
"Yipeng Wang" <yipeng1.wang@intel.com>,
"Yisen Zhuang" <yisen.zhuang@huawei.com>,
"Yuying Zhang" <yuying.zhang@intel.com>,
"Zhe Tao" <zhe.tao@intel.com>
Subject: please help backporting some patches to stable release 22.11.11
Date: Mon, 27 Oct 2025 16:24:53 +0000 [thread overview]
Message-ID: <20251027162455.3711591-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 11/03/25.
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
---
cf454a5794 Bruce Richardson net/ice: fix vector Rx VLAN offload flags
b74d638ab9 Bruce Richardson test/func_reentrancy: fix args to EAL init call
06b296a226 Chengwen Feng net/hns3: fix overwrite mbuf in vector path
7599b94947 Ciara Loftus net/i40e: fix vector Rx queue setup
adb95cc664 David Marchand net/tap: fix build with LTO
a4f1591e93 David Marchand stack: fix unaligned accesses on 128-bit
78ea4b4fcb Gagandeep Singh bus/dpaa: improve cleanup
a0a7903376 Gregory Etelson net/mlx5: fix storage of shared Rx queues
7ba84453ba Jasper Tran O'Leary net/gve: free device resources on close
f9465bdcef Jun Yang net/dpaa2: fix error frame dump
f96273c8e9 Khadem Ullah app/testpmd: stop forwarding in secondary process
f9f773fe2d Mattias Rönnblom bitops: improve power of 2 alignment documentation
4f0abf4b7e Prashant Gupta net/dpaa2: free buffers from error queue
25ef596203 Radu Nicolau crypto/qat: fix ECDH
820ca7361b Rongwei Liu net/mlx5: fix flow aging race condition
33358ccc29 Tathagat Priyadarshi gro: fix payload corruption in coalescing packets
c892964faa Vamsi Attunuru net/octeon_ep: fix device start
ed8eb60c9b Viacheslav Ovsiienko net/mlx5: fix ESP header match after UDP for group 0
96d73a9473 Viacheslav Ovsiienko net/mlx5: fix ESP item validation to match on seqnum
f2f75ffe14 Viacheslav Ovsiienko net/mlx5/hws: fix ESP header match in strict mode
f4905fdcf6 Vladimir Medvedkin fib6: fix memory leak on delete operation
next reply other threads:[~2025-10-27 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 16:24 luca.boccassi [this message]
2025-10-28 10:50 ` Nicolau, Radu
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=20251027162455.3711591-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=14pwcse1224@uetpeshawar.edu.pk \
--cc=aman.deep.singh@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=arkadiuszx.kusztal@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.loftus@intel.com \
--cc=cunming.liang@intel.com \
--cc=david.marchand@redhat.com \
--cc=dsosnowski@nvidia.com \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@intel.com \
--cc=g.singh@nxp.com \
--cc=gage.eads@intel.com \
--cc=getelson@nvidia.com \
--cc=haiyue.wang@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=huangdengdui@huawei.com \
--cc=humin29@huawei.com \
--cc=jiayu.hu@intel.com \
--cc=joshwash@google.com \
--cc=joyce.kong@arm.com \
--cc=jtranoleary@google.com \
--cc=jun.yang@nxp.com \
--cc=junfengg@nvidia.com \
--cc=kai.ji@intel.com \
--cc=keith.wiles@intel.com \
--cc=konstantin.ananyev@huawei.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=kumaraparamesh92@gmail.com \
--cc=leyi.rong@intel.com \
--cc=lihuisong@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=matan@nvidia.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=mb@smartsharesystems.com \
--cc=michaelba@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=nipun.gupta@nxp.com \
--cc=olgas@nvidia.com \
--cc=olivier.matz@6wind.com \
--cc=oulijun@huawei.com \
--cc=pascal.mazon@6wind.com \
--cc=pbhagavatula@marvell.com \
--cc=pnalla@marvell.com \
--cc=prashant.gupta_3@nxp.com \
--cc=radhac@marvell.com \
--cc=radu.nicolau@intel.com \
--cc=rjarry@redhat.com \
--cc=rongweil@nvidia.com \
--cc=rzidane@nvidia.com \
--cc=sachin.saxena@nxp.com \
--cc=sameh.gobriel@intel.com \
--cc=sedara@marvell.com \
--cc=shreyansh.jain@nxp.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=tathagat.dpdk@gmail.com \
--cc=vattunuru@marvell.com \
--cc=vburru@marvell.com \
--cc=viacheslavo@nvidia.com \
--cc=vladimir.medvedkin@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=xavier.huwei@huawei.com \
--cc=xiaoyun.li@intel.com \
--cc=yipeng1.wang@intel.com \
--cc=yisen.zhuang@huawei.com \
--cc=yuying.zhang@intel.com \
--cc=zhe.tao@intel.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).