Linux Kernel Selftest development
 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,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	shuah@kernel.org, anton.makarov11235@gmail.com,
	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 v5 0/4] seg6: add support for SRv6 Headend Reduced
Date: Fri, 29 Jul 2022 11:20:14 +0000	[thread overview]
Message-ID: <165909361463.23060.15495009897031154291.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220727185408.7077-1-andrea.mayer@uniroma2.it>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Wed, 27 Jul 2022 20:54:04 +0200 you wrote:
> This patchset adds support for SRv6 Headend behavior with Reduced
> Encapsulation. It introduces the H.Encaps.Red and H.L2Encaps.Red versions
> of the SRv6 H.Encaps and H.L2Encaps behaviors, according to RFC 8986 [1].
> 
> In details, the patchset is made of:
>  - patch 1/4: add support for SRv6 H.Encaps.Red behavior;
>  - Patch 2/4: add support for SRv6 H.L2Encaps.Red behavior;
>  - patch 2/4: add selftest for SRv6 H.Encaps.Red behavior;
>  - patch 3/4: add selftest for SRv6 H.L2Encaps.Red behavior.
> 
> [...]

Here is the summary with links:
  - [net-next,v5,1/4] seg6: add support for SRv6 H.Encaps.Red behavior
    https://git.kernel.org/netdev/net-next/c/b07c8cdbe918
  - [net-next,v5,2/4] seg6: add support for SRv6 H.L2Encaps.Red behavior
    https://git.kernel.org/netdev/net-next/c/13f0296be8ec
  - [net-next,v5,3/4] selftests: seg6: add selftest for SRv6 H.Encaps.Red behavior
    https://git.kernel.org/netdev/net-next/c/6ab4eb5a52a7
  - [net-next,v5,4/4] selftests: seg6: add selftest for SRv6 H.L2Encaps.Red behavior
    https://git.kernel.org/netdev/net-next/c/95baa4e8fe69

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



      parent reply	other threads:[~2022-07-29 11:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 18:54 [net-next v5 0/4] seg6: add support for SRv6 Headend Reduced Andrea Mayer
2022-07-27 18:54 ` [net-next v5 1/4] seg6: add support for SRv6 H.Encaps.Red behavior Andrea Mayer
2022-07-27 18:54 ` [net-next v5 2/4] seg6: add support for SRv6 H.L2Encaps.Red behavior Andrea Mayer
2022-07-27 18:54 ` [net-next v5 3/4] selftests: seg6: add selftest for SRv6 H.Encaps.Red behavior Andrea Mayer
2022-07-27 18:54 ` [net-next v5 4/4] selftests: seg6: add selftest for SRv6 H.L2Encaps.Red behavior Andrea Mayer
2022-07-29 11:20 ` 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=165909361463.23060.15495009897031154291.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ahabdels.dev@gmail.com \
    --cc=andrea.mayer@uniroma2.it \
    --cc=anton.makarov11235@gmail.com \
    --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