From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Jesse Brandeburg <jbrandeburg@cloudflare.com>
Cc: "Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Jesse Brandeburg <jbrandeb@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
IWL <intel-wired-lan@lists.osuosl.org>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [Intel-wired-lan] [PATCH net v1] ice: stop counting UDP csum mismatch as rx_errors
Date: Tue, 27 Jan 2026 10:25:03 -0800 [thread overview]
Message-ID: <0c198de5-f502-4d12-ba8f-d246b043bb21@intel.com> (raw)
In-Reply-To: <CAB1XECXEQHuU29BaX4j0iMMsz_2SKkG_uV=4Py9FYVxfT0zeuQ@mail.gmail.com>
On 1/27/2026 9:52 AM, Jesse Brandeburg wrote:
> On Mon, Dec 8, 2025 at 2:21 PM Jacob Keller <jacob.e.keller@intel.com> wrote:
>> Right. I agree with Jesse's proposed change. We still keep the stat for
>> the ethtool but we don't report it as a full error to the standard
>> statistics. This matches other drivers from our own products and other
>> vendors.
>
> Hi Tony, can I please get an update on the status of this patch? it's
> been two months for a 1 liner "net" fix.
Hi Jesse, it's part of the PR that I'm working on now; it'll go out
today. It's an isolated and straightforward change that I'm sending it on.
Thanks,
Tony
prev parent reply other threads:[~2026-01-27 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 23:38 [Intel-wired-lan] [PATCH net v1] ice: stop counting UDP csum mismatch as rx_errors Jesse Brandeburg
2025-12-02 22:08 ` Jacob Keller
2025-12-05 8:26 ` Loktionov, Aleksandr
2025-12-05 19:05 ` Jesse Brandeburg
2025-12-05 20:56 ` Loktionov, Aleksandr
2025-12-05 22:44 ` jbrandeburg
2025-12-08 22:20 ` Jacob Keller
2026-01-27 17:52 ` Jesse Brandeburg via Intel-wired-lan
2026-01-27 18:25 ` Tony Nguyen [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=0c198de5-f502-4d12-ba8f-d246b043bb21@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jbrandeb@kernel.org \
--cc=jbrandeburg@cloudflare.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
/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