From: patchwork-bot+netdevbpf@kernel.org
To: Ovidiu Panait <ovidiu.panait.rb@renesas.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, linux@armlinux.org.uk,
rmk+kernel@armlinux.org.uk, maxime.chevallier@bootlin.com,
boon.khai.ng@altera.com, rohan.g.thomas@altera.com,
vladimir.oltean@nxp.com, hayashi.kunihiko@socionext.com,
boon.leong.ong@intel.com, kim.tatt.chuah@intel.com,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/4] net: stmmac: Fix VLAN handling when interface is down
Date: Thu, 05 Mar 2026 03:00:11 +0000 [thread overview]
Message-ID: <177267961155.2494418.12039829007710678123.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260303145828.7845-1-ovidiu.panait.rb@renesas.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 3 Mar 2026 14:58:24 +0000 you wrote:
> VLAN register accesses on the MAC side require the PHY RX clock to be
> active. When the network interface is down, the PHY is suspended and
> the RX clock is unavailable, causing VLAN operations to fail with
> timeouts.
>
> The VLAN core automatically removes VID 0 after the interface goes down
> and re-adds it when it comes back up, so these timeouts happen during
> normal interface down/up:
>
> [...]
Here is the summary with links:
- [net,v3,1/4] net: stmmac: Fix error handling in VLAN add and delete paths
https://git.kernel.org/netdev/net/c/35dfedce442c
- [net,v3,2/4] net: stmmac: Improve double VLAN handling
https://git.kernel.org/netdev/net/c/e38200e361cb
- [net,v3,3/4] net: stmmac: Fix VLAN HW state restore
https://git.kernel.org/netdev/net/c/bd7ad51253a7
- [net,v3,4/4] net: stmmac: Defer VLAN HW configuration when interface is down
https://git.kernel.org/netdev/net/c/2cd70e3968f5
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-03-05 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 14:58 [PATCH net v3 0/4] net: stmmac: Fix VLAN handling when interface is down Ovidiu Panait
2026-03-03 14:58 ` [PATCH net v3 1/4] net: stmmac: Fix error handling in VLAN add and delete paths Ovidiu Panait
2026-03-03 14:58 ` [PATCH net v3 2/4] net: stmmac: Improve double VLAN handling Ovidiu Panait
2026-03-03 14:58 ` [PATCH net v3 3/4] net: stmmac: Fix VLAN HW state restore Ovidiu Panait
2026-03-03 14:58 ` [PATCH net v3 4/4] net: stmmac: Defer VLAN HW configuration when interface is down Ovidiu Panait
2026-03-05 3:00 ` 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=177267961155.2494418.12039829007710678123.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=boon.khai.ng@altera.com \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=kim.tatt.chuah@intel.com \
--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=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ovidiu.panait.rb@renesas.com \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rohan.g.thomas@altera.com \
--cc=vladimir.oltean@nxp.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