From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
f.fainelli@gmail.com, andrew@lunn.ch, vivien.didelot@gmail.com,
olteanv@gmail.com
Subject: Re: [PATCH v2 net-next] net: dsa: track unique bridge numbers across all DSA switch trees
Date: Mon, 23 Aug 2021 11:00:07 +0000 [thread overview]
Message-ID: <162971640791.3591.3908290883435699784.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210819175500.2276709-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Thu, 19 Aug 2021 20:55:00 +0300 you wrote:
> Right now, cross-tree bridging setups work somewhat by mistake.
>
> In the case of cross-tree bridging with sja1105, all switch instances
> need to agree upon a common VLAN ID for forwarding a packet that belongs
> to a certain bridging domain.
>
> With TX forwarding offload, the VLAN ID is the bridge VLAN for
> VLAN-aware bridging, and the tag_8021q TX forwarding offload VID
> (a VLAN which has non-zero VBID bits) for VLAN-unaware bridging.
>
> [...]
Here is the summary with links:
- [v2,net-next] net: dsa: track unique bridge numbers across all DSA switch trees
https://git.kernel.org/netdev/net-next/c/f5e165e72b29
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:[~2021-08-23 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 17:55 [PATCH v2 net-next] net: dsa: track unique bridge numbers across all DSA switch trees Vladimir Oltean
2021-08-23 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=162971640791.3591.3908290883435699784.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.