From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Golle <daniel@makrotopia.org>
Cc: chester.a.unal@arinc9.com, andrew@lunn.ch, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, dqfext@gmail.com,
f.fainelli@gmail.com, arinc.unal@arinc9.com,
sean.wang@mediatek.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net v2 0/5] net: dsa: mt7530: assorted fixes
Date: Tue, 19 May 2026 11:00:15 +0000 [thread overview]
Message-ID: <177918841597.2243186.15077319366803058468.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1778766629.git.daniel@makrotopia.org>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 14 May 2026 15:04:06 +0100 you wrote:
> A batch of small, independent fixes for the MediaTek MT7530 family DSA
> driver, addressing long-standing correctness issues that surface on
> hardware with bridge VLAN filtering enabled, on link-local frame
> reception, and during bridge join/leave transitions.
> ---
> Changes since v1:
> - rework patch 1/5 following up Paolo Abeni and Sashiko reviews
>
> [...]
Here is the summary with links:
- [net,v2,1/5] net: dsa: mt7530: fix FDB entries not aging out with short timeout
https://git.kernel.org/netdev/net/c/e824e40d0e84
- [net,v2,2/5] net: dsa: mt7530: preserve VLAN tags on trapped link-local frames
https://git.kernel.org/netdev/net/c/3ac85bcfd404
- [net,v2,3/5] net: dsa: mt7530: fix CPU port VLAN not being reset to unaware
https://git.kernel.org/netdev/net/c/2c4c76cacc9d
- [net,v2,4/5] net: dsa: mt7530: clear flood flags on bridge leave
(no matching commit)
- [net,v2,5/5] net: dsa: mt7530: untag VLAN-aware bridge PVID
https://git.kernel.org/netdev/net/c/4cb3cd670b2a
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-19 11:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 14:04 [PATCH net v2 0/5] net: dsa: mt7530: assorted fixes Daniel Golle
2026-05-14 14:04 ` [PATCH net v2 1/5] net: dsa: mt7530: fix FDB entries not aging out with short timeout Daniel Golle
2026-05-14 14:04 ` [PATCH net v2 2/5] net: dsa: mt7530: preserve VLAN tags on trapped link-local frames Daniel Golle
2026-05-14 14:04 ` [PATCH net v2 3/5] net: dsa: mt7530: fix CPU port VLAN not being reset to unaware Daniel Golle
2026-05-14 14:05 ` [PATCH net v2 4/5] net: dsa: mt7530: clear flood flags on bridge leave Daniel Golle
2026-05-19 10:53 ` Paolo Abeni
2026-05-14 14:05 ` [PATCH net v2 5/5] net: dsa: mt7530: untag VLAN-aware bridge PVID Daniel Golle
2026-05-19 11: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=177918841597.2243186.15077319366803058468.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arinc.unal@arinc9.com \
--cc=chester.a.unal@arinc9.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.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