From: patchwork-bot+netdevbpf@kernel.org
To: Alexey Charkov <alchark@gmail.com>
Cc: kevinbrace@bracecomputerlab.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, robh@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: via-rhine: Stop the NIC on platform device shutdown
Date: Thu, 19 Nov 2026 00:10:05 +0000 [thread overview]
Message-ID: <179504700528.2637749.17488188558430878185.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261113-vt8500-rhine-shutdown-v1-1-9448ea9548ec@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 13 Nov 2026 17:01:05 +0400 you wrote:
> Close a running interface on platform device shutdown, so that the chip
> stops its receive DMA before kexec hands its memory to the next kernel.
> Do it in the driver, as the platform (OF) variant lacks a .shutdown
> callback and nothing else stops it, unlike for PCI, where the core
> clears bus mastering ahead of kexec.
>
> Keep incoming frames from landing in receive buffers the old kernel had
> allocated: on a WonderMedia WM8950 board, broadcast traffic alone
> corrupts the next kernel at random points as it decompresses and boots,
> hanging about a third of kexec attempts early on, e.g. with
> "unrecognized/unsupported processor variant".
>
> [...]
Here is the summary with links:
- [net] net: via-rhine: Stop the NIC on platform device shutdown
https://git.kernel.org/netdev/net/c/3d10dc3ae1f7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-19 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 13:01 [PATCH net] net: via-rhine: Stop the NIC on platform device shutdown Alexey Charkov
2026-11-19 0: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=179504700528.2637749.17488188558430878185.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alchark@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kevinbrace@bracecomputerlab.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.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