patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Shani Peretz <shperetz@nvidia.com>
To: "Loftus, Ciara" <ciara.loftus@intel.com>, dpdk stable <stable@dpdk.org>
Subject: RE: please help backporting some patches to stable release 23.11.6
Date: Tue, 6 Jan 2026 09:56:25 +0000	[thread overview]
Message-ID: <MW4PR12MB7484AAC58A9EFD0A348763B0BF87A@MW4PR12MB7484.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DM3PPF7D18F34A179A8EA942AA8F13A16CB8E86A@DM3PPF7D18F34A1.namprd11.prod.outlook.com>



> -----Original Message-----
> From: Loftus, Ciara <ciara.loftus@intel.com>
> Sent: Monday, 5 January 2026 13:15
> To: dpdk stable <stable@dpdk.org>
> Cc: Shani Peretz <shperetz@nvidia.com>
> Subject: RE: please help backporting some patches to stable release 23.11.6
> 
> External email: Use caution opening links or attachments
> 
> 
> > 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
> > 12b050defa  Chengwen Feng    app/dma-perf: check buffer size
> > cca4c3bc3f  Chengwen Feng    app/dma-perf: fix stopping device
> > 431bc9c42e  Ciara Loftus     net/iavf: remove extra stores in AVX-512 VLAN
> > offload
> 
> The above commit 431bc9c42e should not be backported.
> Tx VLAN offload is disabled in the iavf AVX-512 path in
> 23.11 (see commit efe1b63775e8 net/iavf: fix VLAN insertion in vector path).
> Because of this the optimisation in the proposed backport patch would be to
> no effect, so I don't think it should be backported.
> 
> Thanks,
> Ciara
> 

Okay, thanks Ciara!


> > 0e3c389b9e  Gagandeep Singh  bus/dpaa: do proper cleanup of frame
> > queues on shutdown 7ba84453ba  Jasper Tran O'Leary net/gve: free
> > device resources on close
> > 6280a30607  Jiawen Wu        net/ngbe: fix checksum error counter
> > 02c9cc1012  Jiawen Wu        net/txgbe: filter FDIR match flex bytes for tunnel
> > b9ad8a6e72  Jiawen Wu        net/txgbe: fix checksum error counter
> > c9a341034a  Jiawen Wu        net/txgbe: fix FDIR filter for SCTP tunnel
> > a2d4de2710  Jiawen Wu        net/txgbe: fix FDIR input mask
> > f9465bdcef  Jun Yang         net/dpaa2: fix error frame dump
> > 97e2e198b9  Nawal Kishor     rawdev: fix device ID retrieval failure handling
> > 327682174e  Nupur Uttarwar   net/mlx5: skip Rx control flow tables in
> > isolated mode
> > 4f0abf4b7e  Prashant Gupta   net/dpaa2: free buffers from error queue
> > 253174309f  Radu Nicolau     crypto/qat: fix source buffer alignment
> > 820ca7361b  Rongwei Liu      net/mlx5: fix flow aging race condition
> > 3eec7a797f  Rongwei Liu      net/mlx5: remove counter alignment
> > d762a8fbbd  Satheesh Paul    net/cnxk: fix port ID default action
> > 743bbd3bd2  Sunil Kumar Kori net/ice: fix Tx packet prepare
> > 74348d7ad2  Vamsi Attunuru   net/octeon_ep: fix mbuf data offset update
> > f4905fdcf6  Vladimir Medvedkin fib6: fix memory leak on delete
> > operation

  reply	other threads:[~2026-01-06  9:56 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
2026-01-06  9:55       ` Shani Peretz
2026-01-05 11:14   ` Loftus, Ciara
2026-01-06  9:56     ` Shani Peretz [this message]
     [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=MW4PR12MB7484AAC58A9EFD0A348763B0BF87A@MW4PR12MB7484.namprd12.prod.outlook.com \
    --to=shperetz@nvidia.com \
    --cc=ciara.loftus@intel.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).