From: patchwork-bot+netdevbpf@kernel.org
To: Andrea Mayer <andrea.mayer@uniroma2.it>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@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,
liuhangbin@gmail.com
Subject: Re: [net-next v2 0/2] seg6: add NEXT-C-SID support for SRv6 End.X behavior
Date: Wed, 16 Aug 2023 02:00:23 +0000 [thread overview]
Message-ID: <169215122333.15326.393610409728204600.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230812180926.16689-1-andrea.mayer@uniroma2.it>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 12 Aug 2023 20:09:24 +0200 you wrote:
> In the Segment Routing (SR) architecture a list of instructions, called
> segments, can be added to the packet headers to influence the forwarding and
> processing of the packets in an SR enabled network.
>
> Considering the Segment Routing over IPv6 data plane (SRv6) [1], the segment
> identifiers (SIDs) are IPv6 addresses (128 bits) and the segment list (SID
> List) is carried in the Segment Routing Header (SRH). A segment may correspond
> to a "behavior" that is executed by a node when the packet is received.
> The Linux kernel currently supports a large subset of the behaviors described
> in [2] (e.g., End, End.X, End.T and so on).
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] seg6: add NEXT-C-SID support for SRv6 End.X behavior
https://git.kernel.org/netdev/net-next/c/7458575a07f1
- [net-next,v2,2/2] selftests: seg6: add selftest for NEXT-C-SID flavor in SRv6 End.X behavior
https://git.kernel.org/netdev/net-next/c/1c53717c8074
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:[~2023-08-16 2:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 18:09 [net-next v2 0/2] seg6: add NEXT-C-SID support for SRv6 End.X behavior Andrea Mayer
2023-08-12 18:09 ` [net-next v2 1/2] " Andrea Mayer
2023-08-14 7:49 ` Hangbin Liu
2023-08-14 16:16 ` David Ahern
2023-08-12 18:09 ` [net-next v2 2/2] selftests: seg6: add selftest for NEXT-C-SID flavor in " Andrea Mayer
2023-08-14 16:29 ` David Ahern
2023-08-16 2:00 ` 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=169215122333.15326.393610409728204600.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=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paolo.lungaroni@uniroma2.it \
--cc=shuah@kernel.org \
--cc=stefano.salsano@uniroma2.it \
/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