From: luca.boccassi@gmail.com
To: dpdk <dev@dpdk.org>
Cc: "dpdk stable" <stable@dpdk.org>,
"Andrew Bailey" <abailey@iol.unh.edu>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Luca Vizzarro" <luca.vizzarro@arm.com>,
"Patrick Robb" <probb@iol.unh.edu>,
"Paul Szczepanek" <paul.szczepanek@arm.com>,
"Vipin Varghese" <vipin.varghese@amd.com>
Subject: please help backporting some patches to stable release 24.11.5
Date: Thu, 26 Mar 2026 12:59:58 +0000 [thread overview]
Message-ID: <20260326130000.2254853-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 24.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 24.11 branch, or
- Indicate that the patch should not be backported
Please do either of the above by 2026/04/01.
You can find the a temporary work-in-progress branch of the coming 24.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 24.11] foo/bar: fix baz
With git format-patch, this can be achieved by appending the parameter:
--subject-prefix='PATCH 24.11'
Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
FYI, branch 24.11 is located at tree:
https://git.dpdk.org/dpdk-stable
Thanks.
Luca Boccassi
---
874312e261 Patrick Robb dts: avoid resources conflict on quick stop/start
bc15a33eee Vipin Varghese doc: update AMD EPYC guide
next reply other threads:[~2026-03-26 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 12:59 luca.boccassi [this message]
2026-03-27 14:50 ` please help backporting some patches to stable release 24.11.5 Patrick Robb
2026-04-01 14:58 ` Patrick Robb
-- strict thread matches above, loose matches on Subject: below --
2026-03-31 21:30 luca.boccassi
2026-03-19 22:11 luca.boccassi
2026-02-20 15:40 luca.boccassi
2026-02-20 16:01 ` Kishore Padmanabha
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=20260326130000.2254853-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=abailey@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=stable@dpdk.org \
--cc=vipin.varghese@amd.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