patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Shani Peretz <shperetz@nvidia.com>, dpdk stable <stable@dpdk.org>,
	"skori@marvell.com" <skori@marvell.com>
Subject: RE: please help backporting some patches to stable release 23.11.6
Date: Mon, 5 Jan 2026 08:48:40 +0000	[thread overview]
Message-ID: <DS0PR11MB7309185F7F288B71ACDC2D259786A@DS0PR11MB7309.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MW4PR12MB7484521AF59ED56F04A14F1ABFBCA@MW4PR12MB7484.namprd12.prod.outlook.com>



> -----Original Message-----
> From: Shani Peretz <shperetz@nvidia.com>
> Sent: Tuesday, December 30, 2025 11:07 AM
> To: dpdk stable <stable@dpdk.org>; Richardson, Bruce
> <bruce.richardson@intel.com>; skori@marvell.com
> Subject: RE: please help backporting some patches to stable release 23.11.6
> 
> 
> 
> > -----Original Message-----
> > From: Shani Peretz <shperetz@nvidia.com>
> > Sent: Thursday, 25 December 2025 11:54
> > To: dpdk stable <stable@dpdk.org>

<snip>

> > Subject: please help backporting some patches to stable release 23.11.6
> >
> > 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/31/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
> >
> > ---
> > 8a8c02d2bb  Anatoly Burakov  vfio: fix custom containers in multiprocess
> 
> > bd96307d15  Bruce Richardson net/fm10k: fix Tx packet prepare
> > 19d7188f6f Bruce Richardson net/ixgbe: fix Tx packet prepare
> > 743bbd3bd2  Sunil Kumar Kori net/ice: fix Tx packet prepare
> 
> Hey Bruce/ Sunil,
> 
> I noticed that the patches were dropped from the 24.11 release and wanted
> to make sure it's okay to drop them from 23.11 as well.
> 
> Thanks,
> Shani
> 
Yes, I think that should be fine.

/Bruce

  reply	other threads:[~2026-01-05  8:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-23  8:24 Shani Peretz
2025-12-23  8:26 ` Shani Peretz
2025-12-25  9:54 ` Shani Peretz
2025-12-29  2:55   ` Jiawen Wu
2025-12-30 14:49     ` Shani Peretz
2025-12-31  6:32       ` Jiawen Wu
2025-12-31  9:41         ` Jiawen Wu
2025-12-30 11:06   ` Shani Peretz
2026-01-05  8:48     ` Richardson, Bruce [this message]
2026-01-06  9:55       ` Shani Peretz
2026-01-05 11:14   ` Loftus, Ciara
2026-01-06  9:56     ` 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=DS0PR11MB7309185F7F288B71ACDC2D259786A@DS0PR11MB7309.namprd11.prod.outlook.com \
    --to=bruce.richardson@intel.com \
    --cc=shperetz@nvidia.com \
    --cc=skori@marvell.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;
as well as URLs for NNTP newsgroup(s).