From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew@lunn.ch,
claudiu.manoil@nxp.com, alexandre.belloni@bootlin.com,
UNGLinuxDriver@microchip.com, robert.hodaszi@digi.com
Subject: Re: [PATCH net] net: dsa: restore dsa_software_vlan_untag() ability to operate on VLAN-untagged traffic
Date: Thu, 19 Dec 2024 03:30:31 +0000 [thread overview]
Message-ID: <173457903151.1807897.16925032481407031771.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241216135059.1258266-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 16 Dec 2024 15:50:59 +0200 you wrote:
> Robert Hodaszi reports that locally terminated traffic towards
> VLAN-unaware bridge ports is broken with ocelot-8021q. He is describing
> the same symptoms as for commit 1f9fc48fd302 ("net: dsa: sja1105: fix
> reception from VLAN-unaware bridges").
>
> For context, the set merged as "VLAN fixes for Ocelot driver":
> https://lore.kernel.org/netdev/20240815000707.2006121-1-vladimir.oltean@nxp.com/
>
> [...]
Here is the summary with links:
- [net] net: dsa: restore dsa_software_vlan_untag() ability to operate on VLAN-untagged traffic
https://git.kernel.org/netdev/net/c/16f027cd40ee
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-12-19 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 13:50 [PATCH net] net: dsa: restore dsa_software_vlan_untag() ability to operate on VLAN-untagged traffic Vladimir Oltean
2024-12-19 3:30 ` patchwork-bot+netdevbpf [this message]
2024-12-19 15:07 ` Vladimir Oltean
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=173457903151.1807897.16925032481407031771.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robert.hodaszi@digi.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