patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'dpdk stable'" <stable@dpdk.org>,
	"'Shani Peretz'" <shperetz@nvidia.com>
Subject: RE: please help backporting some patches to stable release 23.11.6
Date: Mon, 29 Dec 2025 10:55:45 +0800	[thread overview]
Message-ID: <03c401dc786e$a0eb8ec0$e2c2ac40$@trustnetic.com> (raw)
In-Reply-To: <20251225095426.366416-1-shperetz@nvidia.com>

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.

> 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/




  reply	other threads:[~2025-12-29  2:55 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 [this message]
2025-12-30 14:49     ` Shani Peretz
2025-12-31  6:32       ` Jiawen Wu
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='03c401dc786e$a0eb8ec0$e2c2ac40$@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).