mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yibo Dong <dong100@mucse.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, vadim.fedorenko@linux.dev,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	yaojun@mucse.com
Subject: Re: [PATCH net] net: rnpgbe: Accept link-down events without speed magic
Date: Thu, 29 Oct 2026 11:30:04 +0000	[thread overview]
Message-ID: <179327340432.1769177.12829102670928563036.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <C2DFBBF04F1DCFD2+20261026075445.920572-1-dong100@mucse.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Mon, 26 Oct 2026 15:54:45 +0800 you wrote:
> The interface can continue reporting carrier up after the link goes
> down because the driver ignores the firmware's link-down notification.
> 
> Firmware reports link-down events with a zero port_magic and no
> valid speed or duplex information. The driver requires ST_VALID_MAGIC
> for every link event and returns before updating the cached link state
> when this check fails. It also writes an invalid driver snapshot to
> firmware instead of acknowledging the link-down state.
> 
> [...]

Here is the summary with links:
  - [net] net: rnpgbe: Accept link-down events without speed magic
    https://git.kernel.org/netdev/net/c/6815a2513eff

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



      parent reply	other threads:[~2026-10-29 11:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  7:54 Dong Yibo
2026-10-26  8:00 ` netdev-bot+sinfo
2026-10-26  9:26   ` Yibo Dong
2026-10-28 12:40     ` Simon Horman
2026-10-29 11:30 ` 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=179327340432.1769177.12829102670928563036.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dong100@mucse.com \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vadim.fedorenko@linux.dev \
    --cc=yaojun@mucse.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
all inboxes | Powered by JetHome®