From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: "Akhil Goyal" <gakhil@marvell.com>,
"Archana Muniganti" <marchana@marvell.com>,
"Arkadiusz Kusztal" <arkadiuszx.kusztal@intel.com>,
"Ayuj Verma" <ayverma@marvell.com>,
"Bruce Richardson" <bruce.richardson@intel.com>,
"Erik Gabriel Carrillo" <erik.g.carrillo@intel.com>,
"Fan Zhang" <fanzhang.oss@gmail.com>,
"Gage Eads" <gage.eads@intel.com>,
"Gowrishankar Muthukrishnan" <gmuthukrishn@marvell.com>,
"Harry van Haaren" <harry.van.haaren@intel.com>,
"Jerin Jacob" <jerinj@marvell.com>,
"Kanaka Durga Kotamarthy" <kkotamarthy@marvell.com>,
"Kevin Liu" <kevinx.liu@intel.com>,
"Kiran Kumar K" <kirankumark@marvell.com>,
"Liang Ma" <liangma@liangbit.com>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"Mingjin Ye" <mingjinx.ye@intel.com>,
"Nithin Dabilpuram" <ndabilpuram@marvell.com>,
"Nithinsen Kaithakadan" <nkaithakadan@marvell.com>,
"Pavan Nikhilesh" <pbhagavatula@marvell.com>,
"Peter Mccarthy" <peter.mccarthy@intel.com>,
"Pravin Pathak" <pravin.pathak@intel.com>,
"Qi Zhang" <qi.z.zhang@intel.com>,
"Rahul Bhansali" <rbhansali@marvell.com>,
"Ray Kinsella" <mdr@ashroe.eu>,
"Satha Rao" <skoteshwar@marvell.com>,
"Shally Verma" <shallyv@marvell.com>,
"Srujana Challa" <schalla@marvell.com>,
"Steve Yang" <stevex.yang@intel.com>,
"Sunil Kumar Kori" <skori@marvell.com>,
"Tejasree Kondoj" <ktejasree@marvell.com>,
"Timothy McDaniel" <timothy.mcdaniel@intel.com>,
"Vidya Sagar Velumuri" <vvelumuri@marvell.com>
Subject: please help backporting some patches to stable release 22.11.9
Date: Mon, 30 Jun 2025 13:29:28 +0100 [thread overview]
Message-ID: <20250630122929.1134098-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 07/07/25.
You can find the a temporary work-in-progress branch of the coming 22.11.9
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
---
653ef76297 Gowrishankar Muthukrishnan test/crypto: fix RSA vector as per RFC 8017
3734cf22ab Mattias Rönnblom eventdev: fix flag types consistency
a84f23cfb5 Mingjin Ye net/ice: fix handling empty DCF RSS hash
a1efd31b0f Nithinsen Kaithakadan common/cnxk: fix AES-CTR salt handling
a8b1b99ab2 Pravin Pathak event/dlb2: fix credit release race condition
e31d467957 Pravin Pathak event/dlb2: fix public symbol namespace
9891a50af0 Pravin Pathak event/dlb2: fix QID depth xstat
9bebc33703 Rahul Bhansali net/cnxk: fix lock for security session operations
next reply other threads:[~2025-06-30 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 12:29 luca.boccassi [this message]
2025-06-30 19:15 ` Pathak, Pravin
-- strict thread matches above, loose matches on Subject: below --
2025-06-12 21:15 luca.boccassi
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=20250630122929.1134098-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=ayverma@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=erik.g.carrillo@intel.com \
--cc=fanzhang.oss@gmail.com \
--cc=gage.eads@intel.com \
--cc=gakhil@marvell.com \
--cc=gmuthukrishn@marvell.com \
--cc=harry.van.haaren@intel.com \
--cc=jerinj@marvell.com \
--cc=kevinx.liu@intel.com \
--cc=kirankumark@marvell.com \
--cc=kkotamarthy@marvell.com \
--cc=ktejasree@marvell.com \
--cc=liangma@liangbit.com \
--cc=marchana@marvell.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=mdr@ashroe.eu \
--cc=mingjinx.ye@intel.com \
--cc=ndabilpuram@marvell.com \
--cc=nkaithakadan@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=peter.mccarthy@intel.com \
--cc=pravin.pathak@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=rbhansali@marvell.com \
--cc=schalla@marvell.com \
--cc=shallyv@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=stable@dpdk.org \
--cc=stevex.yang@intel.com \
--cc=timothy.mcdaniel@intel.com \
--cc=vvelumuri@marvell.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).