From: Kevin Traynor <ktraynor@redhat.com>
To: dpdk stable <stable@dpdk.org>,
Bruce Richardson <bruce.richardson@intel.com>,
Sunil Kumar Kori <skori@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>,
Luca Boccassi <bluca@debian.org>,
Shani Peretz <shperetz@nvidia.com>
Subject: Re: please help backporting some patches to stable release 24.11.4
Date: Wed, 3 Dec 2025 12:23:11 +0000 [thread overview]
Message-ID: <ffa94955-4473-4b51-98c7-5492db422cd7@redhat.com> (raw)
In-Reply-To: <20251201145523.633988-1-ktraynor@redhat.com>
On 01/12/2025 14:55, Kevin Traynor wrote:
> 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 24.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 24.11 branch, or
> - Indicate that the patch should not be backported
>
> Please do either of the above by 12/04/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
> 0e3c389b9e Gagandeep Singh bus/dpaa: do proper cleanup of frame queues on shutdown
> 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
Hi Sunil/Bruce,
These 3 commits ^^^ all have Fixes: tags pointing way back to adding tx
prep in the drivers and because of that they are flagged for backport to
LTS branches.
To me the commit (referenced in messages) that removed the NULL check
066f3d9cc21c ("ethdev: remove callback checks from fast path") caused
the issue and should be the Fixes: tag.
That also seems to be what was correctly done for 9cd1dcc49eb3
("drivers/net: fix Tx packet prepare").
066f3d9cc21c ("ethdev: remove callback checks from fast path") is not in
LTS branches so in that case we don't need any fixes for it on LTS.
With that, I will drop these 3 patches from requiring backport to 24.11
branch. If any one thinks different let me know.
thanks,
Kevin.
> 5a753913e0 Monendra Singh Kushwaha common/cnxk: fix inline device write operation
> 3e48adc135 Pavan Nikhilesh event/cnxk: fix Rx offload flags
>
>
next prev parent reply other threads:[~2025-12-03 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 14:55 Kevin Traynor
2025-12-03 12:23 ` Kevin Traynor [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-21 15:04 Kevin Traynor
2025-11-25 10:36 ` Loftus, Ciara
2025-11-25 11:05 ` Kevin Traynor
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=ffa94955-4473-4b51-98c7-5492db422cd7@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=jerinj@marvell.com \
--cc=shperetz@nvidia.com \
--cc=skori@marvell.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).