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, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
shuah@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
bpf@vger.kernel.org, stefano.salsano@uniroma2.it,
paolo.lungaroni@uniroma2.it, ahabdels.dev@gmail.com
Subject: Re: [net-next v2 0/3] seg6: add NEXT-C-SID support for SRv6 End behavior
Date: Tue, 20 Sep 2022 10:50:16 +0000 [thread overview]
Message-ID: <166367101624.31197.16175014864853693907.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220912171619.16943-1-andrea.mayer@uniroma2.it>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 12 Sep 2022 19:16:16 +0200 you wrote:
> The Segment Routing (SR) architecture is based on loose source routing.
> 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.
> In SRv6 (Segment Routing over IPv6 data plane) [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/3] seg6: add netlink_ext_ack support in parsing SRv6 behavior attributes
https://git.kernel.org/netdev/net-next/c/e2a8ecc45165
- [net-next,v2,2/3] seg6: add NEXT-C-SID support for SRv6 End behavior
https://git.kernel.org/netdev/net-next/c/848f3c0d4769
- [net-next,v2,3/3] selftests: seg6: add selftest for NEXT-C-SID flavor in SRv6 End behavior
https://git.kernel.org/netdev/net-next/c/19d6356ab3f0
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:[~2022-09-20 10:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 17:16 [net-next v2 0/3] seg6: add NEXT-C-SID support for SRv6 End behavior Andrea Mayer
2022-09-12 17:16 ` [net-next v2 1/3] seg6: add netlink_ext_ack support in parsing SRv6 behavior attributes Andrea Mayer
2022-09-16 16:43 ` David Ahern
2022-09-12 17:16 ` [net-next v2 2/3] seg6: add NEXT-C-SID support for SRv6 End behavior Andrea Mayer
2022-09-16 16:48 ` David Ahern
2022-09-20 10:43 ` Paolo Abeni
2022-09-12 17:16 ` [net-next v2 3/3] selftests: seg6: add selftest for NEXT-C-SID flavor in " Andrea Mayer
2022-09-16 16:50 ` David Ahern
2022-09-20 10:50 ` 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=166367101624.31197.16175014864853693907.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ahabdels.dev@gmail.com \
--cc=andrea.mayer@uniroma2.it \
--cc=bpf@vger.kernel.org \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 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).