From: patchwork-bot+netdevbpf@kernel.org
To: Andrea Mayer <andrea.mayer@uniroma2.it>
Cc: davem@davemloft.net, dsahern@kernel.org, kuznet@ms2.inr.ac.ru,
yoshfuji@linux-ipv6.org, kuba@kernel.org, shuah@kernel.org,
shrijeet@gmail.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, natechancellor@gmail.com,
stefano.salsano@uniroma2.it, paolo.lungaroni@cnit.it,
ahabdels.dev@gmail.com
Subject: Re: [net-next v4 0/8] seg6: add support for SRv6 End.DT4/DT6 behavior
Date: Fri, 04 Dec 2020 21:40:26 +0000 [thread overview]
Message-ID: <160711802655.19007.16256732742816656137.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201202130517.4967-1-andrea.mayer@uniroma2.it>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 2 Dec 2020 14:05:09 +0100 you wrote:
> This patchset provides support for the SRv6 End.DT4 and End.DT6 (VRF mode)
> behaviors.
>
> The SRv6 End.DT4 behavior is used to implement multi-tenant IPv4 L3 VPNs. It
> decapsulates the received packets and performs IPv4 routing lookup in the
> routing table of the tenant. The SRv6 End.DT4 Linux implementation leverages a
> VRF device in order to force the routing lookup into the associated routing
> table.
> The SRv6 End.DT4 behavior is defined in the SRv6 Network Programming [1].
>
> [...]
Here is the summary with links:
- [net-next,v4,1/8] vrf: add mac header for tunneled packets when sniffer is attached
https://git.kernel.org/netdev/net-next/c/048939088220
- [net-next,v4,2/8] seg6: improve management of behavior attributes
https://git.kernel.org/netdev/net-next/c/964adce526a4
- [net-next,v4,3/8] seg6: add support for optional attributes in SRv6 behaviors
https://git.kernel.org/netdev/net-next/c/0a3021f1d4e5
- [net-next,v4,4/8] seg6: add callbacks for customizing the creation/destruction of a behavior
https://git.kernel.org/netdev/net-next/c/cfdf64a03406
- [net-next,v4,5/8] seg6: add support for the SRv6 End.DT4 behavior
https://git.kernel.org/netdev/net-next/c/664d6f86868b
- [net-next,v4,6/8] seg6: add VRF support for SRv6 End.DT6 behavior
https://git.kernel.org/netdev/net-next/c/20a081b7984c
- [net-next,v4,7/8] selftests: add selftest for the SRv6 End.DT4 behavior
https://git.kernel.org/netdev/net-next/c/2195444e09b4
- [net-next,v4,8/8] selftests: add selftest for the SRv6 End.DT6 (VRF) behavior
https://git.kernel.org/netdev/net-next/c/2bc035538e16
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-12-04 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 13:05 [net-next v4 0/8] seg6: add support for SRv6 End.DT4/DT6 behavior Andrea Mayer
2020-12-02 13:05 ` [net-next v4 1/8] vrf: add mac header for tunneled packets when sniffer is attached Andrea Mayer
2020-12-02 13:05 ` [net-next v4 2/8] seg6: improve management of behavior attributes Andrea Mayer
2020-12-02 13:05 ` [net-next v4 3/8] seg6: add support for optional attributes in SRv6 behaviors Andrea Mayer
2020-12-02 13:05 ` [net-next v4 4/8] seg6: add callbacks for customizing the creation/destruction of a behavior Andrea Mayer
2020-12-02 13:05 ` [net-next v4 5/8] seg6: add support for the SRv6 End.DT4 behavior Andrea Mayer
2020-12-02 13:05 ` [net-next v4 6/8] seg6: add VRF support for SRv6 End.DT6 behavior Andrea Mayer
2020-12-02 13:05 ` [net-next v4 7/8] selftests: add selftest for the SRv6 End.DT4 behavior Andrea Mayer
2020-12-02 13:05 ` [net-next v4 8/8] selftests: add selftest for the SRv6 End.DT6 (VRF) behavior Andrea Mayer
2020-12-04 21:36 ` [net-next v4 0/8] seg6: add support for SRv6 End.DT4/DT6 behavior Jakub Kicinski
2020-12-04 21:40 ` patchwork-bot+netdevbpf [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=160711802655.19007.16256732742816656137.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ahabdels.dev@gmail.com \
--cc=andrea.mayer@uniroma2.it \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=paolo.lungaroni@cnit.it \
--cc=shrijeet@gmail.com \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=stefano.salsano@uniroma2.it \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.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).