From: David Miller <davem@davemloft.net>
To: dsahern@gmail.com
Cc: andrea.mayer@uniroma2.it, dsahern@kernel.org, shrijeet@gmail.com,
kuba@kernel.org, shuah@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
sharpd@cumulusnetworks.com, roopa@cumulusnetworks.com,
didutt@gmail.com, stephen@networkplumber.org,
stefano.salsano@uniroma2.it, paolo.lungaroni@cnit.it,
ahabdels@gmail.com
Subject: Re: [net-next,v1,0/5] Strict mode for VRF
Date: Sat, 20 Jun 2020 17:22:55 -0700 (PDT) [thread overview]
Message-ID: <20200620.172255.1570205815461958163.davem@davemloft.net> (raw)
In-Reply-To: <f13c47d2-6b08-8f73-05d2-755a40fba6a8@gmail.com>
From: David Ahern <dsahern@gmail.com>
Date: Sat, 20 Jun 2020 16:32:53 -0700
> On 6/19/20 3:54 PM, Andrea Mayer wrote:
>> This patch set adds the new "strict mode" functionality to the Virtual
>> Routing and Forwarding infrastructure (VRF). Hereafter we discuss the
>> requirements and the main features of the "strict mode" for VRF.
>>
>
> For the set:
> Acked-by: David Ahern <dsahern@gmail.com>
Series applied to net-next, thanks.
prev parent reply other threads:[~2020-06-21 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 22:54 [net-next,v1,0/5] Strict mode for VRF Andrea Mayer
2020-06-19 22:54 ` [net-next,v1,1/5] l3mdev: add infrastructure for table to VRF mapping Andrea Mayer
2020-06-19 22:54 ` [net-next,v1,2/5] vrf: track associations between VRF devices and tables Andrea Mayer
2020-06-19 22:54 ` [net-next,v1,3/5] vrf: add sysctl parameter for strict mode Andrea Mayer
2020-06-19 22:54 ` [net-next,v1,4/5] vrf: add l3mdev registration for table to VRF device lookup Andrea Mayer
2020-06-19 22:54 ` [net-next,v1,5/5] selftests: add selftest for the VRF strict mode Andrea Mayer
2020-06-20 23:32 ` [net-next,v1,0/5] Strict mode for VRF David Ahern
2020-06-21 0:22 ` 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=20200620.172255.1570205815461958163.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ahabdels@gmail.com \
--cc=andrea.mayer@uniroma2.it \
--cc=didutt@gmail.com \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paolo.lungaroni@cnit.it \
--cc=roopa@cumulusnetworks.com \
--cc=sharpd@cumulusnetworks.com \
--cc=shrijeet@gmail.com \
--cc=shuah@kernel.org \
--cc=stefano.salsano@uniroma2.it \
--cc=stephen@networkplumber.org \
/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).