From: Kishore Padmanabha <kishore.padmanabha@broadcom.com>
To: luca.boccassi@gmail.com, dpdk <dev@dpdk.org>
Cc: dpdk stable <stable@dpdk.org>
Subject: RE: please help backporting some patches to stable release 24.11.5
Date: Fri, 20 Feb 2026 11:01:39 -0500 [thread overview]
Message-ID: <028e16567c50b33338eec58540e9c7b3@mail.gmail.com> (raw)
In-Reply-To: <20260220154044.1704312-1-luca.boccassi@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2444 bytes --]
Hi Luca,
The patch e0f92e31f7 is not required to be backported to 24.11. There has
changes in that part of code that will not allow simple merge of this fix.
This fix is not critical to be ported to older version as it is fixing
stats counters in a specific scenario.
Thanks,
Kishore
-----Original Message-----
From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
Sent: Friday, February 20, 2026 10:41 AM
To: dpdk <dev@dpdk.org>
Cc: dpdk stable <stable@dpdk.org>
Subject: please help backporting some patches to stable release 24.11.5
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 02/27/26.
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=d90e6ae6f936ecdc2fd381
1ff9f26aec7f3c06eb
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
---
f82b3ed6ab Anatoly Burakov net/ixgbe: fix pointer handling in IPsec
ab797d5bcf Bruce Richardson dma/idxd: mark portal pointer as volatile
77bb34e047 Ivan Malov net/sfc: avoid speed reset when setting FEC
in started state
e0f92e31f7 Kishore Padmanabha net/bnxt: fix statistics for high number of
queues
bd2f563dbd Rahul Bhansali common/cnxk: fix duplicated branches
2e79349dcd Song Yoong Siang net/e1000: fix igc launch time calculation
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5493 bytes --]
next prev parent reply other threads:[~2026-02-20 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 15:40 please help backporting some patches to stable release 24.11.5 luca.boccassi
2026-02-20 16:01 ` Kishore Padmanabha [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-19 22:11 luca.boccassi
2026-03-26 12:59 luca.boccassi
2026-03-27 14:50 ` Patrick Robb
2026-04-01 14:58 ` Patrick Robb
2026-03-31 21:30 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=028e16567c50b33338eec58540e9c7b3@mail.gmail.com \
--to=kishore.padmanabha@broadcom.com \
--cc=dev@dpdk.org \
--cc=luca.boccassi@gmail.com \
--cc=stable@dpdk.org \
/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