From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Sunil Kumar Kori <skori@marvell.com>, dpdk stable <stable@dpdk.org>
Cc: Jerin Jacob <jerinj@marvell.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Marchand, David" <david.marchand@redhat.com>,
Luca Boccassi <bluca@debian.org>,
Shani Peretz <shperetz@nvidia.com>
Subject: RE: [EXTERNAL] Re: please help backporting some patches to stable release 24.11.4
Date: Thu, 4 Dec 2025 08:45:27 +0000 [thread overview]
Message-ID: <DS0PR11MB7309D8358F7A70E1AA208F3097A6A@DS0PR11MB7309.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SN7PR18MB3869002B1E8DBE22C87ADFB6B4A6A@SN7PR18MB3869.namprd18.prod.outlook.com>
> -----Original Message-----
> From: Sunil Kumar Kori <skori@marvell.com>
> Sent: Thursday, December 4, 2025 4:44 AM
> To: dpdk stable <stable@dpdk.org>; Richardson, Bruce
> <bruce.richardson@intel.com>
> Cc: Jerin Jacob <jerinj@marvell.com>; Thomas Monjalon
> <thomas@monjalon.net>; Marchand, David <david.marchand@redhat.com>;
> Luca Boccassi <bluca@debian.org>; Shani Peretz <shperetz@nvidia.com>
> Subject: RE: [EXTERNAL] Re: please help backporting some patches to stable
> release 24.11.4
>
> >
> > > 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.
> >
>
> Hi Kevin,
> Yes, I am aligned with above explanation. @Bruce Richardson can comment on
> it for better
> Understanding as these are Intel driver fixes.
>
I'm fine with dropping them.
/Bruce
prev parent reply other threads:[~2025-12-04 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 14:55 Kevin Traynor
2025-12-03 12:23 ` Kevin Traynor
2025-12-04 4:43 ` [EXTERNAL] " Sunil Kumar Kori
2025-12-04 8:45 ` Richardson, Bruce [this message]
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=DS0PR11MB7309D8358F7A70E1AA208F3097A6A@DS0PR11MB7309.namprd11.prod.outlook.com \
--to=bruce.richardson@intel.com \
--cc=bluca@debian.org \
--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).