Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: jMAa8hS83ioD4sD46XKD3RoH7LywRyVayGQX1U+vaezL7QA25B5lS8nFCQBejZI/zeVq8uScE2
 5zNdKxY+7g0bILYTevndOj3+NKVyXk9pX3rTPxB6rbCfj0LTHvlGOH9sIsdh6WQnGOkNj6xIsU
 CE68sDrBqkHz9xQ1xO/6nxHXA7uKK442u7MzIxA/JP/gFPrpu4JGoDUBizY8r/LlgH0v74tUNt
 S9DQBWvRKK+W7m8pagLb3RQLd0WA4mLXURkaZ1LnAGXP5EDqUjBzHHHL4e7kq3T+IiRFVjNptA
 pMw=
Date:   Mon, 12 Oct 2020 13:11:13 +0000
From:   "henrik.bjoernlund@microchip.com" <henrik.bjoernlund@microchip.com>
To:     Nikolay Aleksandrov <nikolay@nvidia.com>
CC:     "bridge@lists.linux-foundation.org" 
        <bridge@lists.linux-foundation.org>,
        "davem@davemloft.net" <davem@davemloft.net>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "jiri@mellanox.com" <jiri@mellanox.com>,
        "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
        Roopa Prabhu <roopa@nvidia.com>,
        "idosch@mellanox.com" <idosch@mellanox.com>,
        "kuba@kernel.org" <kuba@kernel.org>,
        "UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
        "horatiu.vultur@microchip.com" <horatiu.vultur@microchip.com>
Subject: Re: [PATCH net-next v4 06/10] bridge: cfm: Kernel space
 implementation of CFM. CCM frame RX added.
Message-ID: <20201012131113.p54op2ku7r4l54bv@soft-test08>
References: <20201009143530.2438738-1-henrik.bjoernlund@microchip.com>
 <20201009143530.2438738-7-henrik.bjoernlund@microchip.com>
 <2ec76c98813c8190ced9e34b70b46d2dad94d714.camel@nvidia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <2ec76c98813c8190ced9e34b70b46d2dad94d714.camel@nvidia.com>
Precedence: bulk

Thanks for the review.

The 10/09/2020 21:52, Nikolay Aleksandrov wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On Fri, 2020-10-09 at 14:35 +0000, Henrik Bjoernlund wrote:
> > This is the third commit of the implementation of the CFM protocol
> > according to 802.1Q section 12.14.
> >
> > Functionality is extended with CCM frame reception.
> > The MEP instance now contains CCM based status information.
> > Most important is the CCM defect status indicating if correct
> > CCM frames are received with the expected interval.
> >
> > Signed-off-by: Henrik Bjoernlund  <henrik.bjoernlund@microchip.com>
> > Reviewed-by: Horatiu Vultur  <horatiu.vultur@microchip.com>
> > ---
> >  include/uapi/linux/cfm_bridge.h |  10 ++
> >  net/bridge/br_cfm.c             | 269 ++++++++++++++++++++++++++++++++
> >  net/bridge/br_private_cfm.h     |  32 ++++
> >  3 files changed, 311 insertions(+)
> >
> 
> Acked-by: Nikolay Aleksandrov <nikolay@nvidia.com>
> 
> 

-- 
/Henrik