From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: Julien Gomes <julien@arista.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
sharpd@cumulusnetworks.com, nicolas.dichtel@6wind.com
Subject: Re: [PATCH net-next v2 1/4] rtnetlink: add NEWCACHEREPORT message type
Date: Tue, 20 Jun 2017 11:54:16 +0300 [thread overview]
Message-ID: <a65cada1-a796-33fc-018c-bbdbfdef7fb1@cumulusnetworks.com> (raw)
In-Reply-To: <20170619204417.13230-2-julien@arista.com>
On 19/06/17 23:44, Julien Gomes wrote:
> New NEWCACHEREPORT message type to be used for cache reports sent
> via Netlink, effectively allowing splitting cache report reception from
> mroute programming.
>
> Suggested-by: Ryan Halbrook <halbrook@arista.com>
> Signed-off-by: Julien Gomes <julien@arista.com>
> ---
> include/uapi/linux/rtnetlink.h | 3 +++
> security/selinux/nlmsgtab.c | 3 ++-
> 2 files changed, 5 insertions(+), 1 deletion(-)
>
Reviewed-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
next prev parent reply other threads:[~2017-06-20 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 20:44 [PATCH net-next v2 0/4] ipmr/ip6mr: add Netlink notifications on cache reports Julien Gomes
2017-06-19 20:44 ` [PATCH net-next v2 1/4] rtnetlink: add NEWCACHEREPORT message type Julien Gomes
2017-06-20 8:54 ` Nikolay Aleksandrov [this message]
2017-06-19 20:44 ` [PATCH net-next v2 2/4] rtnetlink: add restricted rtnl groups for ipv4 and ipv6 mroute Julien Gomes
2017-06-20 8:56 ` Nikolay Aleksandrov
2017-06-19 20:44 ` [PATCH net-next v2 3/4] ipmr: add netlink notifications on igmpmsg cache reports Julien Gomes
2017-06-20 9:33 ` Nikolay Aleksandrov
2017-06-19 20:44 ` [PATCH net-next v2 4/4] ip6mr: add netlink notifications on mrt6msg " Julien Gomes
2017-06-20 9:37 ` Nikolay Aleksandrov
2017-06-20 19:22 ` [PATCH net-next v2 0/4] ipmr/ip6mr: add Netlink notifications on " David Miller
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=a65cada1-a796-33fc-018c-bbdbfdef7fb1@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=julien@arista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=sharpd@cumulusnetworks.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
all inboxes | Powered by JetHome®