From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@idosch.org>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
davem@davemloft.net, kuba@kernel.org, jiri@nvidia.com,
ivecera@redhat.com, roopa@nvidia.com, nikolay@nvidia.com,
amcohen@nvidia.com, danieller@nvidia.com, petrm@nvidia.com,
mlxsw@nvidia.com, idosch@nvidia.com
Subject: Re: [PATCH net-next 0/9] mlxsw: Add support for 802.1ad bridging
Date: Tue, 01 Dec 2020 23:40:07 +0000 [thread overview]
Message-ID: <160686600727.2300.3935564994527670490.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201129125407.1391557-1-idosch@idosch.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Sun, 29 Nov 2020 14:53:58 +0200 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> 802.1ad, also known as QinQ, is an extension to the 802.1q standard,
> which is concerned with passing possibly 802.1q-tagged packets through
> another VLAN-like tunnel. The format of 802.1ad tag is the same as
> 802.1q, except it uses the EtherType of 0x88a8, unlike 802.1q's 0x8100.
>
> [...]
Here is the summary with links:
- [net-next,1/9] mlxsw: reg: Add Switch Port VLAN Classification Register
https://git.kernel.org/netdev/net-next/c/7e9a6620d5c3
- [net-next,2/9] mlxsw: reg: Add et_vlan field to SPVID register
https://git.kernel.org/netdev/net-next/c/2a5a290d6d94
- [net-next,3/9] mlxsw: spectrum: Only treat 802.1q packets as tagged packets
https://git.kernel.org/netdev/net-next/c/a2ef3ae15834
- [net-next,4/9] mlxsw: Make EtherType configurable when pushing VLAN at ingress
https://git.kernel.org/netdev/net-next/c/3ae7a65b6424
- [net-next,5/9] mlxsw: spectrum_switchdev: Create common functions for VLAN-aware bridge
https://git.kernel.org/netdev/net-next/c/773ce33a4860
- [net-next,6/9] mlxsw: spectrum_switchdev: Add support of QinQ traffic
https://git.kernel.org/netdev/net-next/c/80dfeafd6479
- [net-next,7/9] bridge: switchdev: Notify about VLAN protocol changes
https://git.kernel.org/netdev/net-next/c/22ec19f3aee3
- [net-next,8/9] mlxsw: Add QinQ configuration vetoes
https://git.kernel.org/netdev/net-next/c/09139f67d346
- [net-next,9/9] selftests: forwarding: Add QinQ veto testing
https://git.kernel.org/netdev/net-next/c/008cb2ec4354
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:[~2020-12-01 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 12:53 [PATCH net-next 0/9] mlxsw: Add support for 802.1ad bridging Ido Schimmel
2020-11-29 12:53 ` [PATCH net-next 1/9] mlxsw: reg: Add Switch Port VLAN Classification Register Ido Schimmel
2020-11-29 12:54 ` [PATCH net-next 2/9] mlxsw: reg: Add et_vlan field to SPVID register Ido Schimmel
2020-11-29 12:54 ` [PATCH net-next 3/9] mlxsw: spectrum: Only treat 802.1q packets as tagged packets Ido Schimmel
2020-11-29 12:54 ` [PATCH net-next 4/9] mlxsw: Make EtherType configurable when pushing VLAN at ingress Ido Schimmel
2020-11-29 12:54 ` [PATCH net-next 5/9] mlxsw: spectrum_switchdev: Create common functions for VLAN-aware bridge Ido Schimmel
2020-11-29 12:54 ` [PATCH net-next 6/9] mlxsw: spectrum_switchdev: Add support of QinQ traffic Ido Schimmel
2020-11-29 12:54 ` [PATCH net-next 7/9] bridge: switchdev: Notify about VLAN protocol changes Ido Schimmel
2020-11-30 15:43 ` Ivan Vecera
2020-11-29 12:54 ` [PATCH net-next 8/9] mlxsw: Add QinQ configuration vetoes Ido Schimmel
2020-11-29 12:54 ` [PATCH net-next 9/9] selftests: forwarding: Add QinQ veto testing Ido Schimmel
2020-12-01 23:40 ` 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=160686600727.2300.3935564994527670490.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=bridge@lists.linux-foundation.org \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=idosch@nvidia.com \
--cc=ivecera@redhat.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=petrm@nvidia.com \
--cc=roopa@nvidia.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