From: Guillaume Nault <gnault@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Network Development <netdev@vger.kernel.org>,
Martin Varghese <martin.varghese@nokia.com>
Subject: Re: [PATCH net] selftests: add test script for bareudp tunnels
Date: Fri, 30 Oct 2020 10:39:03 +0100 [thread overview]
Message-ID: <20201030093903.GA5719@pc-2.home> (raw)
In-Reply-To: <CA+FuTSfs1ZsEuu4vKojEU_Bo=DibWDbPPXrw3f=2L6+UAr6UZw@mail.gmail.com>
On Thu, Oct 29, 2020 at 02:11:38PM -0400, Willem de Bruijn wrote:
> On Wed, Oct 28, 2020 at 10:27 PM Guillaume Nault <gnault@redhat.com> wrote:
> >
> > On Wed, Oct 28, 2020 at 07:05:19PM +0100, Guillaume Nault wrote:
> > > Test different encapsulation modes of the bareudp module:
> >
> > BTW, I was assuming that kselftests were like documentation updates,
> > and therefore always suitable for the net tree. If not, the patch
> > applies cleanly to net-next (and I can also repost of course).
>
> I think that's where it belongs.
Hum, do you mean to net or to net-next?
> Very nice test, I don't have any detailed comments. Just one high level:
>
> Are all kernel dependencies for the test captured in
> tools/testing/selftests/net/config? I think mirred is absent, for
> instance
Thanks! I didn't realise that we had this config file. I'll add the
build dependencies in v2.
next prev parent reply other threads:[~2020-10-30 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 18:05 [PATCH net] selftests: add test script for bareudp tunnels Guillaume Nault
2020-10-28 18:34 ` Guillaume Nault
2020-10-29 18:11 ` Willem de Bruijn
2020-10-30 9:39 ` Guillaume Nault [this message]
2020-10-30 12:57 ` Willem de Bruijn
2020-10-30 4:20 ` Varghese, Martin (Nokia - IN/Bangalore)
2020-10-30 9:42 ` Guillaume Nault
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=20201030093903.GA5719@pc-2.home \
--to=gnault@redhat.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=martin.varghese@nokia.com \
--cc=netdev@vger.kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
/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).