All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrea Mayer <andrea.mayer@uniroma2.it>
Cc: davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
	kuba@kernel.org, shuah@kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	stefano.salsano@uniroma2.it, paolo.lungaroni@uniroma2.it,
	ahabdels.dev@gmail.com
Subject: Re: [net-next v1 0/2] seg6: add support for SRv6 End.DT46 Behavior
Date: Fri, 18 Jun 2021 18:40:05 +0000	[thread overview]
Message-ID: <162404160501.23407.2102812799058333171.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210617171645.7970-1-andrea.mayer@uniroma2.it>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Thu, 17 Jun 2021 19:16:43 +0200 you wrote:
> SRv6 End.DT46 Behavior is defined in the IETF RFC 8986 [1] along with SRv6
> End.DT4 and End.DT6 Behaviors.
> 
> The proposed End.DT46 implementation is meant to support the decapsulation
> of both IPv4 and IPv6 traffic coming from a *single* SRv6 tunnel.
> The SRv6 End.DT46 Behavior greatly simplifies the setup and operations of
> SRv6 VPNs in the Linux kernel.
> 
> [...]

Here is the summary with links:
  - [net-next,v1,1/2] seg6: add support for SRv6 End.DT46 Behavior
    https://git.kernel.org/netdev/net-next/c/8b532109bf88
  - [net-next,v1,2/2] selftests: seg6: add selftest for SRv6 End.DT46 Behavior
    https://git.kernel.org/netdev/net-next/c/03a0b567a03d

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-06-18 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 17:16 [net-next v1 0/2] seg6: add support for SRv6 End.DT46 Behavior Andrea Mayer
2021-06-17 17:16 ` [net-next v1 1/2] " Andrea Mayer
2021-06-17 17:16 ` [net-next v1 2/2] selftests: seg6: add selftest " Andrea Mayer
2021-06-18 18: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=162404160501.23407.2102812799058333171.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ahabdels.dev@gmail.com \
    --cc=andrea.mayer@uniroma2.it \
    --cc=davem@davemloft.net \
    --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@uniroma2.it \
    --cc=shuah@kernel.org \
    --cc=stefano.salsano@uniroma2.it \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.