All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Andrea Mayer <andrea.mayer@uniroma2.it>
Cc: "David S. Miller" <davem@davemloft.net>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	David Ahern <dsahern@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
	Anton Makarov <anton.makarov11235@gmail.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org,
	Stefano Salsano <stefano.salsano@uniroma2.it>,
	Paolo Lungaroni <paolo.lungaroni@uniroma2.it>,
	Ahmed Abdelsalam <ahabdels.dev@gmail.com>
Subject: Re: [net-next v3 0/4] seg6: add support for SRv6 Headend Reduced Encapsulation
Date: Tue, 28 Jun 2022 22:10:56 -0700	[thread overview]
Message-ID: <20220628221056.48b5028f@kernel.org> (raw)
In-Reply-To: <20220628113642.3223-1-andrea.mayer@uniroma2.it>

On Tue, 28 Jun 2022 13:36:38 +0200 Andrea Mayer wrote:
>  - patch 2/4: add selftest for SRv6 H.Encaps.Red behavior;
>  - patch 3/4: add selftest for SRv6 H.L2Encaps.Red behavior.

Always great to see selftests. Should they be added to the Makefile?
Otherwise they won't run unless someone manually executes them.

  parent reply	other threads:[~2022-06-29  5:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 11:36 [net-next v3 0/4] seg6: add support for SRv6 Headend Reduced Encapsulation Andrea Mayer
2022-06-28 11:36 ` [net-next v3 1/4] seg6: add support for SRv6 H.Encaps.Red behavior Andrea Mayer
2022-06-28 11:36 ` [net-next v3 2/4] seg6: add support for SRv6 H.L2Encaps.Red behavior Andrea Mayer
2022-06-28 11:36 ` [net-next v3 3/4] selftests: seg6: add selftest for SRv6 H.Encaps.Red behavior Andrea Mayer
2022-06-28 11:36 ` [net-next v3 4/4] selftests: seg6: add selftest for SRv6 H.L2Encaps.Red behavior Andrea Mayer
2022-06-29  5:10 ` Jakub Kicinski [this message]
2022-06-29 11:25   ` [net-next v3 0/4] seg6: add support for SRv6 Headend Reduced Encapsulation Andrea Mayer

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=20220628221056.48b5028f@kernel.org \
    --to=kuba@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=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 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.