patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: "Loftus, Ciara" <ciara.loftus@intel.com>, dpdk stable <stable@dpdk.org>
Subject: Re: please help backporting some patches to stable release 22.11.11
Date: Fri, 31 Oct 2025 13:48:32 +0000	[thread overview]
Message-ID: <14cfd880-4cab-4429-b19d-8eea8ca0d6cc@redhat.com> (raw)
In-Reply-To: <DM3PPF7D18F34A133DA12EDF7A634E0ED108EFAA@DM3PPF7D18F34A1.namprd11.prod.outlook.com>

On 29/10/2025 10:56, Loftus, Ciara wrote:
>>
>> Can authors check your patches in the following list and either:
>>     - Backport your patches to the 22.11 branch, or
>>     - Indicate that the patch should not be backported
> 
> The following commit should not be backported:
> 	7599b94947  Ciara Loftus     net/i40e: fix vector Rx queue setup
> 

Hi Ciara,

Is that also true for other LTS branches also ? It does not apply on
24.11 branch and would need a custom backport.

thanks,
Kevin.

> Thanks,
> Ciara
> 
>>
>> Please do either of the above by 11/03/25.
>>
>> You can find the a temporary work-in-progress branch of the coming 22.11.11
>> 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 22.11] foo/bar: fix baz
>>
>> With git format-patch, this can be achieved by appending the parameter:
>>     --subject-prefix='PATCH 22.11'
>>
>> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>>
>> FYI, branch 22.11 is located at tree:
>>    https://git.dpdk.org/dpdk-stable
>>
>> Thanks.
>>
>> Luca Boccassi
>>
>> ---
>> cf454a5794  Bruce Richardson net/ice: fix vector Rx VLAN offload flags
>> b74d638ab9  Bruce Richardson test/func_reentrancy: fix args to EAL init call
>> 06b296a226  Chengwen Feng    net/hns3: fix overwrite mbuf in vector path
>> 7599b94947  Ciara Loftus     net/i40e: fix vector Rx queue setup
>> adb95cc664  David Marchand   net/tap: fix build with LTO
>> a4f1591e93  David Marchand   stack: fix unaligned accesses on 128-bit
>> 78ea4b4fcb  Gagandeep Singh  bus/dpaa: improve cleanup
>> a0a7903376  Gregory Etelson  net/mlx5: fix storage of shared Rx queues
>> 7ba84453ba  Jasper Tran O'Leary net/gve: free device resources on close
>> f9465bdcef  Jun Yang         net/dpaa2: fix error frame dump
>> f96273c8e9  Khadem Ullah     app/testpmd: stop forwarding in secondary
>> process
>> f9f773fe2d  Mattias Rönnblom bitops: improve power of 2 alignment
>> documentation
>> 4f0abf4b7e  Prashant Gupta   net/dpaa2: free buffers from error queue
>> 25ef596203  Radu Nicolau     crypto/qat: fix ECDH
>> 820ca7361b  Rongwei Liu      net/mlx5: fix flow aging race condition
>> 33358ccc29  Tathagat Priyadarshi gro: fix payload corruption in coalescing
>> packets
>> c892964faa  Vamsi Attunuru   net/octeon_ep: fix device start
>> ed8eb60c9b  Viacheslav Ovsiienko net/mlx5: fix ESP header match after UDP
>> for group 0
>> 96d73a9473  Viacheslav Ovsiienko net/mlx5: fix ESP item validation to match
>> on seqnum
>> f2f75ffe14  Viacheslav Ovsiienko net/mlx5/hws: fix ESP header match in strict
>> mode
>> f4905fdcf6  Vladimir Medvedkin fib6: fix memory leak on delete operation



  reply	other threads:[~2025-10-31 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 16:24 luca.boccassi
2025-10-28 10:50 ` Nicolau, Radu
2025-10-29 10:56 ` Loftus, Ciara
2025-10-31 13:48   ` Kevin Traynor [this message]
2025-10-29 14:29 ` David Marchand
2025-11-02  9:43 ` Gregory Etelson

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=14cfd880-4cab-4429-b19d-8eea8ca0d6cc@redhat.com \
    --to=ktraynor@redhat.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).