From: Jakub Kicinski <kubakici@wp.pl>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, daniel@iogearbox.net,
alexei.starovoitov@gmail.com, hannes@stressinduktion.org,
dsahern@gmail.com, oss-drivers@netronome.com
Subject: Re: [PATCH net-next 2/2] tools: bpf: add bpftool
Date: Thu, 28 Sep 2017 06:59:12 -0700 [thread overview]
Message-ID: <20170928065912.00a9b6a1@cakuba> (raw)
In-Reply-To: <20170926153522.31500-3-jakub.kicinski@netronome.com>
On Tue, 26 Sep 2017 08:35:22 -0700, Jakub Kicinski wrote:
> Add a simple tool for querying and updating BPF objects on the system.
>
> Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> Reviewed-by: Simon Horman <simon.horman@netronome.com>
Dave, I got some late review nitpicks internally which I think are
worth addressing. Would you mind dropping this series? I will post v2
with the cleanups and README included.
next prev parent reply other threads:[~2017-09-28 13:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 15:35 [PATCH net-next 0/2] tools: add bpftool Jakub Kicinski
2017-09-26 15:35 ` [PATCH net-next 1/2] tools: rename tools/net directory to tools/bpf Jakub Kicinski
2017-09-26 21:04 ` Daniel Borkmann
2017-09-26 22:19 ` Alexei Starovoitov
2017-09-26 15:35 ` [PATCH net-next 2/2] tools: bpf: add bpftool Jakub Kicinski
2017-09-26 21:06 ` Daniel Borkmann
2017-09-26 22:24 ` Alexei Starovoitov
2017-09-26 23:02 ` Jakub Kicinski
2017-09-27 10:45 ` Jesper Dangaard Brouer
2017-09-27 10:55 ` Daniel Borkmann
2017-09-27 10:57 ` Jakub Kicinski
2017-09-27 11:19 ` Jesper Dangaard Brouer
2017-09-27 11:49 ` Markus Heiser
2017-09-28 13:59 ` Jakub Kicinski [this message]
2017-09-28 15:48 ` David Miller
2017-09-26 23:32 ` [PATCH net-next 0/2] tools: " David Ahern
2017-09-27 0:44 ` 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=20170928065912.00a9b6a1@cakuba \
--to=kubakici@wp.pl \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=hannes@stressinduktion.org \
--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.