From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.0 required=3.0 tests=BAYES_00,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A6F3CC64E7A for ; Tue, 1 Dec 2020 23:40:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2BD0E2225B for ; Tue, 1 Dec 2020 23:40:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727341AbgLAXks (ORCPT ); Tue, 1 Dec 2020 18:40:48 -0500 Received: from mail.kernel.org ([198.145.29.99]:51312 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727005AbgLAXkr (ORCPT ); Tue, 1 Dec 2020 18:40:47 -0500 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PATCH net-next 0/9] mlxsw: Add support for 802.1ad bridging From: patchwork-bot+netdevbpf@kernel.org Message-Id: <160686600727.2300.3935564994527670490.git-patchwork-notify@kernel.org> Date: Tue, 01 Dec 2020 23:40:07 +0000 References: <20201129125407.1391557-1-idosch@idosch.org> In-Reply-To: <20201129125407.1391557-1-idosch@idosch.org> To: Ido Schimmel 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 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.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 > > 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