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/7] nfp: more set actions and notifier refactor
Date: Wed, 07 Nov 2018 11:46:01 -0800 (PST) [thread overview]
Message-ID: <20181107.114601.2157789423945784235.davem@davemloft.net> (raw)
In-Reply-To: <20181107010734.29935-1-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Tue, 6 Nov 2018 17:07:27 -0800
> This series brings updates to flower offload code. First Pieter adds
> support for setting TTL, ToS, Flow Label and Hop Limit fields in IPv4
> and IPv6 headers.
>
> Remaining 5 patches deal with factoring out netdev notifiers from flower
> code. We already have two instances, and more is coming, so it's time
> to move to one central notifier which then feeds individual feature
> handlers.
>
> I start that part by cleaning up the existing notifiers. Next a central
> notifier is added, and used by flower offloads.
Looks good, series applied, thanks Jakub.
prev parent reply other threads:[~2018-11-08 5:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 1:07 [PATCH net-next 0/7] nfp: more set actions and notifier refactor Jakub Kicinski
2018-11-07 1:07 ` [PATCH net-next 1/7] nfp: flower: add ipv4 set ttl and tos offload Jakub Kicinski
2018-11-07 1:07 ` [PATCH net-next 2/7] nfp: flower: add ipv6 set flow label and hop limit offload Jakub Kicinski
2018-11-07 1:07 ` [PATCH net-next 3/7] nfp: flower: remove unnecessary iteration over devices Jakub Kicinski
2018-11-07 1:07 ` [PATCH net-next 4/7] nfp: flower: don't try to nack device unregister events Jakub Kicinski
2018-11-07 1:07 ` [PATCH net-next 5/7] nfp: flower: make nfp_fl_lag_changels_event() void Jakub Kicinski
2018-11-07 1:07 ` [PATCH net-next 6/7] nfp: register a notifier handler in a central location for the device Jakub Kicinski
2018-11-07 1:07 ` [PATCH net-next 7/7] nfp: flower: use the common netdev notifier Jakub Kicinski
2018-11-07 19:46 ` 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=20181107.114601.2157789423945784235.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;
as well as URLs for NNTP newsgroup(s).