From: patchwork-bot+netdevbpf@kernel.org
To: Gustav Ekelund <gustav.ekelund@axis.com>
Cc: marek.behun@nic.cz, andrew@lunn.ch, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, kernel@axis.com,
gustaek@axis.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: dsa: mv88e6xxx: Reset mv88e6393x force WD event bit
Date: Sun, 02 Apr 2023 12:40:17 +0000 [thread overview]
Message-ID: <168043921731.11869.10697921708685299184.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230331084014.1144597-1-gustav.ekelund@axis.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 31 Mar 2023 10:40:13 +0200 you wrote:
> From: Gustav Ekelund <gustaek@axis.com>
>
> The force watchdog event bit is not cleared during SW reset in the
> mv88e6393x switch. This is a different behavior compared to mv886390 which
> clears the force WD event bit as advertised. This causes a force WD event
> to be handled over and over again as the SW reset following the event never
> clears the force WD event bit.
>
> [...]
Here is the summary with links:
- [net,v2] net: dsa: mv88e6xxx: Reset mv88e6393x force WD event bit
https://git.kernel.org/netdev/net/c/089b91a0155c
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:[~2023-04-02 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 8:40 [PATCH net v2] net: dsa: mv88e6xxx: Reset mv88e6393x force WD event bit Gustav Ekelund
2023-03-31 12:27 ` Andrew Lunn
2023-03-31 12:49 ` Florian Fainelli
2023-04-02 12:40 ` 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=168043921731.11869.10697921708685299184.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gustaek@axis.com \
--cc=gustav.ekelund@axis.com \
--cc=kernel@axis.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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