bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: ast@kernel.org, john.fastabend@gmail.com, yhs@fb.com,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH bpf-next v2 1/6] bpf: improve bpf_redirect_neigh helper description
Date: Fri, 9 Oct 2020 11:24:51 -0700	[thread overview]
Message-ID: <20201009112451.3ce7a6b7@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <8fcc44a98c7600492c5f1fc1e79fccdcf3bfe4d2.1602252399.git.daniel@iogearbox.net>

On Fri,  9 Oct 2020 16:10:10 +0200 Daniel Borkmann wrote:
> + * 		get the	address of the next hop and then relies on the neighbor

FWIW if you have to respin there is a tab in the middle of this line

> + * 		get the	address of the next hop and then relies on the neighbor

Also copied here.

  reply	other threads:[~2020-10-09 18:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 14:10 [PATCH bpf-next v2 0/6] Follow-up BPF helper improvements Daniel Borkmann
2020-10-09 14:10 ` [PATCH bpf-next v2 1/6] bpf: improve bpf_redirect_neigh helper description Daniel Borkmann
2020-10-09 18:24   ` Jakub Kicinski [this message]
2020-10-09 14:10 ` [PATCH bpf-next v2 2/6] bpf: add redirect_peer helper Daniel Borkmann
2020-10-09 14:10 ` [PATCH bpf-next v2 3/6] bpf: allow for map-in-map with dynamic inner array map entries Daniel Borkmann
2020-10-09 17:42   ` Andrii Nakryiko
2020-10-09 18:35     ` Daniel Borkmann
2020-10-09 18:42       ` Andrii Nakryiko
2020-10-09 14:10 ` [PATCH bpf-next v2 4/6] bpf, selftests: add test for different array inner map size Daniel Borkmann
2020-10-09 14:10 ` [PATCH bpf-next v2 5/6] bpf, selftests: make redirect_neigh test more extensible Daniel Borkmann
2020-10-09 14:10 ` [PATCH bpf-next v2 6/6] bpf, selftests: add redirect_peer selftest 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=20201009112451.3ce7a6b7@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dsahern@gmail.com \
    --cc=john.fastabend@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=yhs@fb.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).