patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Shani Peretz <shperetz@nvidia.com>
To: dpdk stable <stable@dpdk.org>
Cc: "Anatoly Burakov" <anatoly.burakov@intel.com>,
	"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
	"Ankit Garg" <nktgrg@google.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>,
	"Gagandeep Singh" <g.singh@nxp.com>,
	"Haiyue Wang" <haiyue.wang@intel.com>,
	"Hemant Agrawal" <hemant.agrawal@nxp.com>,
	"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
	"Jasper Tran O'Leary" <jtranoleary@google.com>,
	"Jeroen de Borst" <jeroendb@google.com>,
	"Joshua Washington" <joshwash@google.com>,
	"Junfeng Guo" <junfengg@nvidia.com>,
	"Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>,
	"Matan Azrad" <matan@nvidia.com>,
	"Michael Baum" <michaelba@nvidia.com>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"Nawal Kishor" <nkishor@marvell.com>,
	"Ori Kam" <orika@nvidia.com>, "Robin Jarry" <rjarry@redhat.com>,
	"Rongwei Liu" <rongweil@nvidia.com>,
	"Rushil Gupta" <rushilg@google.com>,
	"Sachin Saxena" <sachin.saxena@nxp.com>,
	"Sameh Gobriel" <sameh.gobriel@intel.com>,
	"Shreyansh Jain" <shreyansh.jain@nxp.com>,
	"Suanming Mou" <suanmingm@nvidia.com>,
	"Thomas Monjalon" <thomas@monjalon.net>,
	"Vamsi Attunuru" <vattunuru@marvell.com>,
	"Viacheslav Ovsiienko" <viacheslavo@nvidia.com>,
	"Vladimir Medvedkin" <vladimir.medvedkin@intel.com>,
	"Xiaoyun Li" <xiaoyun.li@intel.com>,
	"Yipeng Wang" <yipeng1.wang@intel.com>,
	"Zhe Tao" <zhe.tao@intel.com>,
	"Shani Peretz" <shperetz@nvidia.com>
Subject: please help backporting some patches to stable release 23.11.6
Date: Tue, 23 Dec 2025 10:24:19 +0200	[thread overview]
Message-ID: <20251223082419.261870-1-shperetz@nvidia.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 23.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 23.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 12/28/25.

You can find the a temporary work-in-progress branch of the coming 23.11.6
release at:
    https://github.com/shanipr/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 23.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 23.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 23.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Shani

---
b74d638ab9  Bruce Richardson test/func_reentrancy: fix args to EAL init call - will remove from need backport list
78ea4b4fcb  Gagandeep Singh  bus/dpaa: improve cleanup - new patch was sent and added to 23.11
7ba84453ba  Jasper Tran O'Leary net/gve: free device resources on close
f4a70b449b  Joshua Washington net/gve: add DQO Tx descriptor limit
92d330a3ea  Joshua Washington net/gve: clean when insufficient Tx descriptors
ee06313a50  Joshua Washington net/gve: send whole packet when mbuf is large
97e2e198b9  Nawal Kishor     rawdev: fix device ID retrieval failure handling
820ca7361b  Rongwei Liu      net/mlx5: fix flow aging race condition
74348d7ad2  Vamsi Attunuru   net/octeon_ep: fix mbuf data offset update
f4905fdcf6  Vladimir Medvedkin fib6: fix memory leak on delete operation


             reply	other threads:[~2025-12-23  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-23  8:24 Shani Peretz [this message]
2025-12-23  8:26 ` Shani Peretz
     [not found] <20251221162621.929312-1-shperetz@nvidia.com>
2025-12-22  8:42 ` Richardson, Bruce
2025-12-23  8:27   ` Shani Peretz

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=20251223082419.261870-1-shperetz@nvidia.com \
    --to=shperetz@nvidia.com \
    --cc=anatoly.burakov@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --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=g.singh@nxp.com \
    --cc=haiyue.wang@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jeroendb@google.com \
    --cc=joshwash@google.com \
    --cc=jtranoleary@google.com \
    --cc=junfengg@nvidia.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=matan@nvidia.com \
    --cc=mb@smartsharesystems.com \
    --cc=michaelba@nvidia.com \
    --cc=nkishor@marvell.com \
    --cc=nktgrg@google.com \
    --cc=orika@nvidia.com \
    --cc=rjarry@redhat.com \
    --cc=rongweil@nvidia.com \
    --cc=rushilg@google.com \
    --cc=sachin.saxena@nxp.com \
    --cc=sameh.gobriel@intel.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=stable@dpdk.org \
    --cc=suanmingm@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=vattunuru@marvell.com \
    --cc=viacheslavo@nvidia.com \
    --cc=vladimir.medvedkin@intel.com \
    --cc=xiaoyun.li@intel.com \
    --cc=yipeng1.wang@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).