public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Joyner <eric.joyner@amd.com>
Cc: netdev@vger.kernel.org, brett.creeley@amd.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net] ionic: Rate limit unknown xcvr type messages
Date: Wed, 11 Feb 2026 05:10:04 +0000	[thread overview]
Message-ID: <177078660483.7583.7365563668694669374.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260206224651.1491-1-eric.joyner@amd.com>

Hello:

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

On Fri, 6 Feb 2026 14:46:51 -0800 you wrote:
> Running ethtool repeatedly with a transceiver unknown to the driver or
> firmware will cause the driver to spam the kernel logs with "unknown
> xcvr type" messages which can distract from real issues; and this isn't
> interesting information outside of debugging. Fix this by rate limiting
> the output so that there are still notifications but not so many that
> they flood the log.
> 
> [...]

Here is the summary with links:
  - [net] ionic: Rate limit unknown xcvr type messages
    https://git.kernel.org/netdev/net/c/cdb1634de3bf

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



      reply	other threads:[~2026-02-11  5:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 22:46 [PATCH net] ionic: Rate limit unknown xcvr type messages Eric Joyner
2026-02-11  5:10 ` 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=177078660483.7583.7365563668694669374.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=brett.creeley@amd.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.joyner@amd.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