netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Benc <jbenc@redhat.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
	Alan Maguire <alan.maguire@oracle.com>
Subject: Re: [PATCH bpf] selftests: bpf: xdping is not meant to be run standalone
Date: Mon, 18 Nov 2019 09:18:21 +0100	[thread overview]
Message-ID: <20191118091821.4a1b3faf@redhat.com> (raw)
In-Reply-To: <427e0b06-679e-5621-f828-be545e6ca3b1@iogearbox.net>

On Fri, 15 Nov 2019 23:06:13 +0100, Daniel Borkmann wrote:
> Any objections if I take this to bpf-next as otherwise this will create an ugly
> merge conflict between bpf and bpf-next given selftests have been heavily reworked
> in there.

Should I resend against bpf-next?

 Jiri


  reply	other threads:[~2019-11-18  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 12:42 [PATCH bpf] selftests: bpf: xdping is not meant to be run standalone Jiri Benc
2019-11-15 13:08 ` Toke Høiland-Jørgensen
2019-11-15 14:03   ` Alan Maguire
2019-11-15 22:06 ` Daniel Borkmann
2019-11-18  8:18   ` Jiri Benc [this message]
2019-11-18  9:39     ` Daniel Borkmann

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=20191118091821.4a1b3faf@redhat.com \
    --to=jbenc@redhat.com \
    --cc=alan.maguire@oracle.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --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).