public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Rangoju@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
	Raju <Raju.Rangoju@amd.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, kuba@kernel.org,
	edumazet@google.com, davem@davemloft.net, andrew+netdev@lunn.ch,
	Thomas.Lendacky@amd.com, Shyam-sundar.S-k@amd.com
Subject: Re: [PATCH net v2] amd-xgbe: avoid misleading per-packet error log
Date: Mon, 19 Jan 2026 14:18:35 +0000	[thread overview]
Message-ID: <176883231552.1426077.2769109296574901743.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260114163037.2062606-1-Raju.Rangoju@amd.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 14 Jan 2026 22:00:37 +0530 you wrote:
> On the receive path, packet can be damaged because of buffer
> overflow in Rx FIFO. Avoid misleading per-packet error log when
> packet->errors is set, this can flood the log. Instead, rely on the
> standard rtnl_link_stats64 stats.
> 
> Fixes: c5aa9e3b8156 ("amd-xgbe: Initial AMD 10GbE platform driver")
> Signed-off-by: Raju Rangoju <Raju.Rangoju@amd.com>
> 
> [...]

Here is the summary with links:
  - [net,v2] amd-xgbe: avoid misleading per-packet error log
    https://git.kernel.org/netdev/net/c/c158f985cf6c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-01-19 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 16:30 [PATCH net v2] amd-xgbe: avoid misleading per-packet error log Raju Rangoju
2026-01-19 14:18 ` patchwork-bot+netdevbpf [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=176883231552.1426077.2769109296574901743.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Raju.Rangoju@amd.com \
    --cc=Rangoju@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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