Message ID | 20201027100251.3241719-1-henrik.bjoernlund@microchip.com |
---|---|
Headers | show
Return-Path: <netdev-owner@vger.kernel.org> X-Original-To: patchwork-incoming-netdev@ozlabs.org Delivered-To: patchwork-incoming-netdev@ozlabs.org Authentication-Results: ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=vger.kernel.org (client-ip=23.128.96.18; helo=vger.kernel.org; envelope-from=netdev-owner@vger.kernel.org; receiver=<UNKNOWN>) Authentication-Results: ozlabs.org; dmarc=fail (p=quarantine dis=none) header.from=microchip.com Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=microchip.com header.i=@microchip.com header.a=rsa-sha256 header.s=mchp header.b=nQDTzEjT; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by ozlabs.org (Postfix) with ESMTP id 4CL6kC1qjQz9sTf for <patchwork-incoming-netdev@ozlabs.org>; Tue, 27 Oct 2020 21:04:19 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2437310AbgJ0KEQ (ORCPT <rfc822;patchwork-incoming-netdev@ozlabs.org>); Tue, 27 Oct 2020 06:04:16 -0400 Received: from esa2.microchip.iphmx.com ([68.232.149.84]:34850 "EHLO esa2.microchip.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2411294AbgJ0KEP (ORCPT <rfc822;netdev@vger.kernel.org>); Tue, 27 Oct 2020 06:04:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1603793054; x=1635329054; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=f7mhXRoSJu/byey8hhjFwfYfaY2ar+qTEyEgWFGPu/Q=; b=nQDTzEjTb3vLNqeGv/qnuBOEAwdzwNWfjEePuOpCYmhabrwAvk6rb4+r Dl8ckSXvFuPh5BxNX0ut/8evbGqGGnwmaa2u6CDZaU2PsqJn2FWh/2uhE v9Cwj4a/Ii+Nei4SYWXKhXeKtUloch/ak7O64uUQosDjcqJgAKAD9y/zC DXl0/T2q8rqdppB0UP/cNWSAP40I9Qk9hYvTbYqWYlc4vu9OPyNUeJ1UL Ga7Q3mbrUdBEnoyCyQUSD7BjEr5CdT8u8nAB6Rj+3FcuG0e1Mbc/qd8N3 z5QzCjQYJ36L7Qi795TUiQkBpI/wSQFsh5zIystykPUofVs4KaJptVkGO A==; IronPort-SDR: PUYIE4ZtooF/uJtrbjxXbxMfeJ3rPDiZ2REo0l977m82l5OzxjF2f81e1Slph9cbAsEgOYDCGZ 7sE+W+Q63vMnm4L8U2obdP79xFocnOc9Pf9GOUvcOrnJWTvtYqKTjc0khf7FggoQpyZ1LhdLLT dClMFISxgWV/Tg79tWvsPGNxX+tfCeFVJyUT/QxbqXFLlx0KOqxE2IlAYB+aJzsOiAJST2Avqn rUSd2rUQJG9froe9wTrlU4liw9ZcAXIiQCHZGiLzv4lTsc1XC6IIE1WGTvf/6nWrt1zF/PK0hu UMY= X-IronPort-AV: E=Sophos;i="5.77,423,1596524400"; d="scan'208";a="94040326" Received: from smtpout.microchip.com (HELO email.microchip.com) ([198.175.253.82]) by esa2.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 27 Oct 2020 03:04:14 -0700 Received: from chn-vm-ex01.mchp-main.com (10.10.85.143) by chn-vm-ex02.mchp-main.com (10.10.85.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Tue, 27 Oct 2020 03:04:13 -0700 Received: from soft-test08.microsemi.net (10.10.115.15) by chn-vm-ex01.mchp-main.com (10.10.85.143) with Microsoft SMTP Server id 15.1.1979.3 via Frontend Transport; Tue, 27 Oct 2020 03:04:11 -0700 From: Henrik Bjoernlund <henrik.bjoernlund@microchip.com> To: <davem@davemloft.net>, <kuba@kernel.org>, <roopa@nvidia.com>, <nikolay@nvidia.com>, <jiri@mellanox.com>, <idosch@mellanox.com>, <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>, <bridge@lists.linux-foundation.org>, <UNGLinuxDriver@microchip.com> CC: Henrik Bjoernlund <henrik.bjoernlund@microchip.com>, Horatiu Vultur <horatiu.vultur@microchip.com> Subject: [PATCH net-next v7 00/10] net: bridge: cfm: Add support for Connectivity Fault Management(CFM) Date: Tue, 27 Oct 2020 10:02:41 +0000 Message-ID: <20201027100251.3241719-1-henrik.bjoernlund@microchip.com> X-Mailer: git-send-email 2.28.0 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: <netdev.vger.kernel.org> X-Mailing-List: netdev@vger.kernel.org |
Series |
net: bridge: cfm: Add support for Connectivity Fault Management(CFM)
|
expand
|
On Tue, 27 Oct 2020 10:02:41 +0000 Henrik Bjoernlund wrote: > Connectivity Fault Management (CFM) is defined in 802.1Q > section 12.14. > > Connectivity Fault Management (CFM) comprises capabilities for > detecting, verifying, and isolating connectivity failures in Virtual > Bridged Networks. These capabilities can be used in networks > operated by multiple independent organizations, each with restricted > management access to each other’s equipment. Applied, thanks!