From: Magnus Leatti <magnusleatti@kernelriot.com>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: Nicolai Buchwitz <nb@tipi-net.de>, Yao Zi <me@ziyao.cc>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: stmmac: dwmac-motorcomm: mask the MISC interrupt
Date: Mon, 2 Nov 2026 05:53:03 -0300 [thread overview]
Message-ID: <20261102085303.5391-1-magnusleatti@kernelriot.com> (raw)
In-Reply-To: <20d4a3c3-99fa-4659-8d5d-eb5eefcf6545@bootlin.com>
On 11/2/26 09:22, Maxime Chevallier wrote:
> Can you test this, sent a few days ago ? I also saw that storm, but it didn't
> seem to be motorcomm specific :
Thanks, I missed it. It fixes the hang here with MISC left unmasked,
so masking is not needed. I replied with a Tested-by on your thread.
Please drop this patch.
For context, I ran into the hang while benchmarking the glue for a few
patches I plan to send once net-next opens, among them Wake-on-LAN from
S5, which does not work on this board today.
next prev parent reply other threads:[~2026-11-02 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 8:09 Magnus Leatti
2026-11-02 8:22 ` Maxime Chevallier
2026-11-02 8:53 ` Magnus Leatti [this message]
2026-11-02 8:29 ` Nicolai Buchwitz
2026-11-02 8:36 ` Maxime Chevallier
2026-11-02 9:02 ` Magnus Leatti
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=20261102085303.5391-1-magnusleatti@kernelriot.com \
--to=magnusleatti@kernelriot.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=me@ziyao.cc \
--cc=muhammad.nazim.amirul.nazle.asmade@altera.com \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
/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®