patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Loftus, Ciara" <ciara.loftus@intel.com>
To: dpdk stable <stable@dpdk.org>
Cc: Kevin Traynor <ktraynor@redhat.com>
Subject: RE: please help backporting some patches to stable release 24.11.4
Date: Tue, 25 Nov 2025 10:36:28 +0000	[thread overview]
Message-ID: <DM3PPF7D18F34A1A8A828C4BD2F0805DBC18ED1A@DM3PPF7D18F34A1.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20251121150455.526395-1-ktraynor@redhat.com>

> 
> 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 11/27/25.
> 
> You can find the a temporary work-in-progress branch of the coming 24.11.4
> release at:
>     https://github.com/kevintraynor/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.
> 
> Kevin
> 
> ---
> f2f75ffe14  Viacheslav Ovsiienko net/mlx5/hws: fix ESP header match in strict
> mode
> 08b83e84e1  Nithinsen Kaithakadan crypto/cnxk: fix TLS mbuf
> 8a8c02d2bb  Anatoly Burakov  vfio: fix custom containers in multiprocess
> d1b3b66967  Chengwen Feng    app/dma-perf: fix on-flight DMA when
> verifying data
> cca4c3bc3f  Chengwen Feng    app/dma-perf: fix stopping device
> 0e3c389b9e  Gagandeep Singh  bus/dpaa: do proper cleanup of frame queues
> on shutdown
> 822bd84cea  Howard Wang      net/r8169: fix static analysis warnings
> 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 24.11 (see
commit 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

> 3bf9f0f9f0  Viacheslav Ovsiienko net/mlx5: fix control flow leakage for
> external SQ
> a4ad0eba9d  Wathsala Vithanage ring: establish safe partial order in default
> mode
> 66d5f96278  Wathsala Vithanage ring: establish safe partial order in HTS
> mode
> 36b69b5f95  Wathsala Vithanage ring: establish safe partial order in RTS mode
> 
> 743bbd3bd2  Sunil Kumar Kori net/ice: fix Tx packet prepare
> 19d7188f6f  Bruce Richardson net/ixgbe: fix Tx packet prepare
> bd96307d15  Bruce Richardson net/fm10k: fix Tx packet prepare
> ^^^ These seem to need:
>     066f3d9cc21c ("ethdev: remove callback checks from fast path")
> but I'm not sure if we should backport that (also it doesn apply cleanly)
> 
> 5a753913e0  Monendra Singh Kushwaha common/cnxk: fix inline device
> write operation
> 860f6c63db  Maayan Kashani   net/mlx5: fix device start error handling


  reply	other threads:[~2025-11-25 10:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 15:04 Kevin Traynor
2025-11-25 10:36 ` Loftus, Ciara [this message]
2025-11-25 11:05   ` Kevin Traynor
  -- strict thread matches above, loose matches on Subject: below --
2025-10-31 15:03 Kevin Traynor

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=DM3PPF7D18F34A1A8A828C4BD2F0805DBC18ED1A@DM3PPF7D18F34A1.namprd11.prod.outlook.com \
    --to=ciara.loftus@intel.com \
    --cc=ktraynor@redhat.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).