From: Andrew Lunn <andrew@lunn.ch>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
netdev-bot+sinfo@kernel.org, netdev@vger.kernel.org,
Paolo Abeni <pabeni@redhat.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Serge Semin <fancer.lancer@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Nicolai Buchwitz <nb@tipi-net.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: stmmac: unwind the WoL IRQ after a safety IRQ request failure
Date: Wed, 7 Oct 2026 21:34:03 +0200 [thread overview]
Message-ID: <8cd651e5-d240-4663-8361-c3b939d664e9@lunn.ch> (raw)
In-Reply-To: <CADvTj4ozfxA3E13g5sV2tPogDk=S+VOyf_PAXZVQyaozoe3O0w@mail.gmail.com>
> Should I re-spin this on net-next with the fixes tag dropped? Or does
> this apply as-is on net-next?
You should respin.
We get hundreds of patches a day. Maintainers have no time to see if
is applies cleanly, compiles and passes basic smoke tests on hardware.
Andrew
next prev parent reply other threads:[~2026-10-07 19:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 7:06 [PATCH net v2] net: stmmac: unwind the WoL IRQ after a safety IRQ request failure James Hilliard
2026-10-06 7:09 ` netdev-bot+sinfo
2026-10-06 7:14 ` James Hilliard
2026-10-06 22:52 ` Jakub Kicinski
2026-10-06 23:17 ` James Hilliard
2026-10-07 0:57 ` Andrew Lunn
2026-10-07 1:27 ` James Hilliard
2026-10-07 12:46 ` Andrew Lunn
2026-10-07 17:00 ` James Hilliard
2026-10-07 18:32 ` Andrew Lunn
2026-10-07 19:31 ` James Hilliard
2026-10-07 19:34 ` Andrew Lunn [this message]
2026-10-07 1:10 ` Jakub Kicinski
2026-10-06 7:50 ` Maxime Chevallier
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=8cd651e5-d240-4663-8361-c3b939d664e9@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=nb@tipi-net.de \
--cc=netdev-bot+sinfo@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox