From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH net-next 0/3] nfp: flower: repr link state
Date: Wed, 03 Jan 2018 12:18:25 -0500 (EST) [thread overview]
Message-ID: <20180103.121825.2053669223295456241.davem@davemloft.net> (raw)
In-Reply-To: <20180103031901.4165-1-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
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.
prev parent reply other threads:[~2018-01-03 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 3:18 [PATCH net-next 0/3] nfp: flower: repr link state Jakub Kicinski
2018-01-03 3:18 ` [PATCH net-next 1/3] nfp: flower: obtain repr link state only from firmware Jakub Kicinski
2018-01-03 3:19 ` [PATCH net-next 2/3] nfp: add repr_preclean callback Jakub Kicinski
2018-01-03 3:19 ` [PATCH net-next 3/3] nfp: flower: implement the PORT_REIFY message Jakub Kicinski
2018-01-03 17:18 ` David Miller [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=20180103.121825.2053669223295456241.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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