From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next 0/3] nfp: flower: repr link state Date: Wed, 03 Jan 2018 12:18:25 -0500 (EST) Message-ID: <20180103.121825.2053669223295456241.davem@davemloft.net> References: <20180103031901.4165-1-jakub.kicinski@netronome.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, oss-drivers@netronome.com To: jakub.kicinski@netronome.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:34194 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751077AbeACRS3 (ORCPT ); Wed, 3 Jan 2018 12:18:29 -0500 In-Reply-To: <20180103031901.4165-1-jakub.kicinski@netronome.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Jakub Kicinski Date: Tue, 2 Jan 2018 19:18:58 -0800 > Dirk says: > > This series provides two updates towards the link state of reprs in > the flower nfp app. > > Patch #1 improves the way link state is reported for reprs. Instead of > starting with an assumed 'UP' state, always assume the link state is > 'DOWN' and then modify this only on events received from firmware. > > Patch #2 adds a new nfp_app hook, repr_preclean. This callback is > executed before reprs are removed from the app context and is executed > per repr. > > Patch #3 implements the new REIFY control message, used to indicate > when reprs are created and destroyed. Firmware uses these messages > to prevent communication about any particular port when the driver > doesn't know about the repr yet or anymore. Series applied, thanks.