netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Guillaume Nault <gnault@redhat.com>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	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 08:57:00 -0400	[thread overview]
Message-ID: <CA+FuTSe2GYxxX2hckeYwiDjBfCdF-ZXXqizRF=ATboLZAAdaJQ@mail.gmail.com> (raw)
In-Reply-To: <20201030093903.GA5719@pc-2.home>

On Fri, Oct 30, 2020 at 5:39 AM Guillaume Nault <gnault@redhat.com> wrote:
>
> 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?

Sorry, that wasn't very clear. I meant net-next

  reply	other threads:[~2020-10-30 12:57 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
2020-10-30 12:57       ` Willem de Bruijn [this message]
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='CA+FuTSe2GYxxX2hckeYwiDjBfCdF-ZXXqizRF=ATboLZAAdaJQ@mail.gmail.com' \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=davem@davemloft.net \
    --cc=gnault@redhat.com \
    --cc=kuba@kernel.org \
    --cc=martin.varghese@nokia.com \
    --cc=netdev@vger.kernel.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).