From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'Shani Peretz'" <shperetz@nvidia.com>,
"'dpdk stable'" <stable@dpdk.org>
Subject: RE: please help backporting some patches to stable release 23.11.6
Date: Wed, 31 Dec 2025 14:32:58 +0800 [thread overview]
Message-ID: <040901dc7a1f$4dca9850$e95fc8f0$@trustnetic.com> (raw)
In-Reply-To: <MW4PR12MB748414C80D61B7B53BECDF90BFBCA@MW4PR12MB7484.namprd12.prod.outlook.com>
On Tue, Dec 30, 2025 10:49 PM, Shani Peretz wrote:
> > -----Original Message-----
> > From: Jiawen Wu <jiawenwu@trustnetic.com>
> > Sent: Monday, 29 December 2025 4:56
> > To: 'dpdk stable' <stable@dpdk.org>; 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
> >
> >
> > Hi Shani Peretz,
> >
> > > 6280a30607 Jiawen Wu net/ngbe: fix checksum error counter
> > > b9ad8a6e72 Jiawen Wu net/txgbe: fix checksum error counter
> >
> > I'll send patches to backport these two patches.
>
> In those two commits that you sent it appears that the variables:
> + struct txgbe_rx_queue *rxq;
> + uint64_t rx_csum_err = 0;
>
> were added in *_dev_xstats_get_() instead of *_dev_xstats_get(). I've fixed this, and now the build is passing successfully.
> Could you also please check the following commits to ensure everything is in order?
> https://github.com/DPDK/dpdk-stable/commit/209262228bb231b6ff951ef34edfdd246654e89e
> https://github.com/DPDK/dpdk-stable/commit/772691c32fb29d64fc012efb7a59820557f335e1
Something strange happened when I applied the patches...
Thanks for the fixes, these two commits are perfect.
>
> >
> > > 02c9cc1012 Jiawen Wu net/txgbe: filter FDIR match flex bytes for tunnel
> > > c9a341034a Jiawen Wu net/txgbe: fix FDIR filter for SCTP tunnel
> > > a2d4de2710 Jiawen Wu net/txgbe: fix FDIR input mask
> >
> > But these FDIR related patches merge has conflicts because two patches were
> > missed in release 23.11.5.
> >
> > [1] https://inbox.dpdk.org/stable/20250731022631.1830705-1-
> > jiawenwu@trustnetic.com/
> > [2] https://inbox.dpdk.org/stable/20250731022631.1830705-2-
> > jiawenwu@trustnetic.com/
> >
> >
>
> Hey,
>
> Sorry I missed those patches, I've added them now.
> I rebased the patches on top of them, but the patch "net/txgbe: fix FDIR input mask" has some build issues (struct rte_ipv6_hdr was
> changed, and the patch uses the new fields)
> Could you send a fix for 23.11?
Okay, I'll send it today.
next prev parent reply other threads:[~2025-12-31 6:33 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 [this message]
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
[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='040901dc7a1f$4dca9850$e95fc8f0$@trustnetic.com' \
--to=jiawenwu@trustnetic.com \
--cc=shperetz@nvidia.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).