All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>, netdev@vger.kernel.org
Cc: alexei.starovoitov@gmail.com, daniel@iogearbox.net,
	oss-drivers@netronome.com, brouer@redhat.com
Subject: Re: [PATCH net-next v4 0/3] tools: add bpftool
Date: Wed, 4 Oct 2017 20:26:01 -0700	[thread overview]
Message-ID: <aa472a38-5293-c0c0-4476-117dfa169f1d@gmail.com> (raw)
In-Reply-To: <20171005031005.15364-1-jakub.kicinski@netronome.com>

On 10/4/17 8:10 PM, Jakub Kicinski wrote:
> Hi!
> 
> This set adds bpftool to the tools/ directory.  The first 
> patch renames tools/net to tools/bpf, the second one adds 
> the new code, while the third adds simple documentation.
> 
> v4:
>  - rename docs *.txt -> *.rst (Jesper).
> v3:
>  - address Alexei's comments about output and docs.
> v2:
>  - report names, map ids, load time, uid;
>  - add docs/man pages;
>  - general cleanups & fixes.
> 
> Jakub Kicinski (3):
>   tools: rename tools/net directory to tools/bpf
>   tools: bpf: add bpftool
>   tools: bpftool: add documentation
> 

LGTM. Thanks for the work, Jakub.

Acked-by: David Ahern <dsahern@gmail.com>

  parent reply	other threads:[~2017-10-05  3:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05  3:10 [PATCH net-next v4 0/3] tools: add bpftool Jakub Kicinski
2017-10-05  3:10 ` [PATCH net-next v4 1/3] tools: rename tools/net directory to tools/bpf Jakub Kicinski
2017-10-05  3:10 ` [PATCH net-next v4 2/3] tools: bpf: add bpftool Jakub Kicinski
2017-10-05  3:10 ` [PATCH net-next v4 3/3] tools: bpftool: add documentation Jakub Kicinski
2017-10-05  3:26 ` David Ahern [this message]
2017-10-05  4:46 ` [PATCH net-next v4 0/3] tools: add bpftool David Miller
2017-10-05 16:02   ` Jakub Kicinski

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=aa472a38-5293-c0c0-4476-117dfa169f1d@gmail.com \
    --to=dsahern@gmail.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=brouer@redhat.com \
    --cc=daniel@iogearbox.net \
    --cc=jakub.kicinski@netronome.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.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 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.