DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: dpdk stable <stable@dpdk.org>
Cc: dev@dpdk.org, Akhil Goyal <gakhil@marvell.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Anoob Joseph <anoobj@marvell.com>,
	Anurag Mandal <anurag.mandal@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Chengwen Feng <fengchengwen@huawei.com>,
	Ciara Loftus <ciara.loftus@intel.com>,
	David Marchand <david.marchand@redhat.com>,
	Erik Gabriel Carrillo <erik.g.carrillo@intel.com>,
	Ferruh Yigit <ferruh.yigit@amd.com>,
	Gagandeep Singh <g.singh@nxp.com>,
	Geoff Thorpe <geoff.thorpe@nxp.com>,
	Harman Kalra <hkalra@marvell.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Jun Yang <jun.yang@nxp.com>,
	mb@smartsharesystems.com, Ori Kam <orika@nvidia.com>,
	Qiming Yang <qiming.yang@intel.com>,
	Qi Zhang <qi.z.zhang@intel.com>, Rohit Raj <rohit.raj@nxp.com>,
	Roy Pledge <roy.pledge@nxp.com>,
	Sachin Saxena <sachin.saxena@nxp.com>,
	Shaiq Wani <shaiq.wani@intel.com>,
	Shreyansh Jain <shreyansh.jain@nxp.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	Tyler Retzlaff <roretzla@linux.microsoft.com>,
	Volodymyr Fialko <vfialko@marvell.com>
Subject: please help backporting some patches to stable release 24.11.9
Date: Thu,  5 Nov 2026 17:20:10 +0000	[thread overview]
Message-ID: <20261105172011.1419239-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-11-10.

You can find the a temporary work-in-progress branch of the coming 24.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 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

---
c8325b3939  Anatoly Burakov  ethdev: fix MACsec item support in flow conversion
b1ebf0fc1b  Anatoly Burakov  net/iavf: centralize memory management for flows
7495d45fb2  David Marchand   bus/fslmc: fix interrupt leak in DPIO cleanup
0e03411639  David Marchand   test: defer timer initialization
dd82d0e9c4  Jun Yang         bus/dpaa: fix hang on FQ shutdown
a5dd495b8e  Shaiq Wani       net/intel: fix idpf Tx payload corruption in split queue
670ead3dd1  Stephen Hemminger eal/linux: fix FD leak in alarm subsystem
8c8da52f31  Thomas Monjalon  eal: enforce internal API check with Clang 14

                 reply	other threads:[~2026-11-05 17:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261105172011.1419239-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=anatoly.burakov@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=anoobj@marvell.com \
    --cc=anurag.mandal@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@amd.com \
    --cc=g.singh@nxp.com \
    --cc=gakhil@marvell.com \
    --cc=geoff.thorpe@nxp.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=hkalra@marvell.com \
    --cc=jun.yang@nxp.com \
    --cc=mb@smartsharesystems.com \
    --cc=orika@nvidia.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=rohit.raj@nxp.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=roy.pledge@nxp.com \
    --cc=sachin.saxena@nxp.com \
    --cc=shaiq.wani@intel.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=vfialko@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