From: patchwork-bot+netdevbpf@kernel.org
To: Maciej W. Rozycki <macro@orcam.me.uk>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] FDDI: defza: Sanitise the reset safety timer
Date: Thu, 14 May 2026 00:50:05 +0000 [thread overview]
Message-ID: <177871980555.3899557.7004016793675338471.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2605061216430.46195@angie.orcam.me.uk>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 9 May 2026 22:04:50 +0100 (BST) you wrote:
> The reset actions of the DEFZA adapters are exceedingly slow, taking up
> to 30 seconds to complete by the device spec and typically in the range
> of 10 seconds in reality, as required for the device RTOS to boot, still
> quite a lot. Therefore a state machine is used that's interrupt driven,
> however a safety mechanism is required in case of adapter malfunction,
> so that if no state change interrupt has arrived in time, then the
> situation is taken care of.
>
> [...]
Here is the summary with links:
- [net-next] FDDI: defza: Sanitise the reset safety timer
https://git.kernel.org/netdev/net/c/4694efc41641
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-05-14 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 21:04 [PATCH net-next] FDDI: defza: Sanitise the reset safety timer Maciej W. Rozycki
2026-05-13 1:06 ` Jakub Kicinski
2026-05-13 15:29 ` Maciej W. Rozycki
2026-05-14 0:18 ` Jakub Kicinski
2026-05-14 0:50 ` 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=177871980555.3899557.7004016793675338471.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.