From: Jakub Kicinski <kubakici@wp.pl>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: netdev@vger.kernel.org, daniel@iogearbox.net,
alexei.starovoitov@gmail.com, oss-drivers@netronome.com
Subject: Re: [PATCH net-next v2 0/3] tools: add bpftool
Date: Tue, 3 Oct 2017 17:48:22 -0700 [thread overview]
Message-ID: <20171003174822.214e4337@cakuba> (raw)
In-Reply-To: <20171003201942.GH25388@kernel.org>
On Tue, 3 Oct 2017 17:19:42 -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Oct 02, 2017 at 04:11:27PM -0700, Jakub Kicinski escreveu:
> > 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.
> >
> > v2:
> > - report names, map ids, load time, uid;
> > - add docs/man pages;
> > - general cleanups & fixes.
> >
> > Thanks to David Beckett for help with docs and testing.
>
> Why not call it just 'bpf'?
bpftool was suggested as a better name, I don't really mind either way.
next prev parent reply other threads:[~2017-10-04 0:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 23:11 [PATCH net-next v2 0/3] tools: add bpftool Jakub Kicinski
2017-10-02 23:11 ` [PATCH net-next v2 1/3] tools: rename tools/net directory to tools/bpf Jakub Kicinski
2017-10-02 23:11 ` [PATCH net-next v2 2/3] tools: bpf: add bpftool Jakub Kicinski
2017-10-02 23:11 ` [PATCH net-next v2 3/3] tools: bpftool: add documentation Jakub Kicinski
2017-10-03 0:55 ` Alexei Starovoitov
2017-10-03 1:35 ` Jakub Kicinski
2017-10-03 4:29 ` Alexei Starovoitov
2017-10-03 15:39 ` David Ahern
2017-10-03 16:01 ` Daniel Borkmann
2017-10-03 16:09 ` David Ahern
2017-10-03 17:57 ` [RFC 1/2] bpf: move instruction printing into a separate file Jakub Kicinski
2017-10-03 17:57 ` [RFC 2/2] tools: bpftool: use the kernel's instruction printer Jakub Kicinski
2017-10-03 19:32 ` [RFC 1/2] bpf: move instruction printing into a separate file Daniel Borkmann
2017-10-03 20:14 ` Alexei Starovoitov
2017-10-04 0:20 ` [RFC] bpf: remove global verifier state Jakub Kicinski
2017-10-04 2:52 ` Alexei Starovoitov
2017-10-04 3:24 ` Eric Dumazet
2017-10-04 3:43 ` Alexei Starovoitov
2017-10-04 19:13 ` Daniel Borkmann
2017-10-04 21:57 ` Jakub Kicinski
2017-10-04 22:40 ` Alexei Starovoitov
2017-10-03 14:15 ` [PATCH net-next v2 3/3] tools: bpftool: add documentation Daniel Borkmann
2017-10-03 20:19 ` [PATCH net-next v2 0/3] tools: add bpftool Arnaldo Carvalho de Melo
2017-10-04 0:48 ` Jakub Kicinski [this message]
2017-10-04 11:40 ` Arnaldo Carvalho de Melo
2017-10-04 4:33 ` David Miller
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=20171003174822.214e4337@cakuba \
--to=kubakici@wp.pl \
--cc=acme@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--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 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).