From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Quentin Monnet <quentin.monnet@netronome.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org, oss-drivers@netronome.com,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jesper Dangaard Brouer <brouer@redhat.com>,
Stanislav Fomichev <sdf@google.com>
Subject: Re: [PATCH bpf-next v4 0/9] tools: bpftool: add probes for system and device
Date: Wed, 16 Jan 2019 16:56:57 -0800 [thread overview]
Message-ID: <20190116165646.0453396d@cakuba.netronome.com> (raw)
In-Reply-To: <20190116165513.566973f1@cakuba.netronome.com>
On Wed, 16 Jan 2019 16:55:13 -0800, Jakub Kicinski wrote:
> On Wed, 16 Jan 2019 14:21:10 +0000, Quentin Monnet wrote:
> > tools/bpf/bpftool/feature.c | 764 ++++++++++++++++++
>
> should we perhaps git mv feature.c probe.c ? (if you create a commit
> with just a move right after the first commit which adds the file git
> will figure out its a rename, and the squash this rename into first
> commit).
Ah, scratch that, we got "feature probe".
prev parent reply other threads:[~2019-01-17 0:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 14:21 [PATCH bpf-next v4 0/9] tools: bpftool: add probes for system and device Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 1/9] tools: bpftool: add basic probe capability, probe syscall availability Quentin Monnet
2019-01-17 0:28 ` Jakub Kicinski
2019-01-17 10:02 ` Quentin Monnet
2019-01-17 10:11 ` Daniel Borkmann
2019-01-16 14:21 ` [PATCH bpf-next v4 2/9] tools: bpftool: add probes for /proc/ eBPF parameters Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 3/9] tools: bpftool: add probes for kernel configuration options Quentin Monnet
2019-01-17 0:34 ` Jakub Kicinski
2019-01-17 10:03 ` Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 4/9] tools: bpftool: add probes for eBPF program types Quentin Monnet
2019-01-17 0:42 ` Jakub Kicinski
2019-01-17 9:27 ` Daniel Borkmann
2019-01-17 10:04 ` Quentin Monnet
2019-01-17 14:11 ` Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 5/9] tools: bpftool: add probes for eBPF map types Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 6/9] tools: bpftool: add probes for eBPF helper functions Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 7/9] tools: bpftool: add C-style "#define" output for probes Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 8/9] tools: bpftool: add probes for a network device Quentin Monnet
2019-01-16 14:42 ` Jesper Dangaard Brouer
2019-01-16 14:59 ` Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 9/9] tools: bpftool: add bash completion for bpftool probes Quentin Monnet
2019-01-16 17:15 ` [PATCH bpf-next v4 0/9] tools: bpftool: add probes for system and device Stanislav Fomichev
2019-01-17 10:06 ` Quentin Monnet
2019-01-17 0:55 ` Jakub Kicinski
2019-01-17 0:56 ` Jakub Kicinski [this message]
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=20190116165646.0453396d@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=acme@kernel.org \
--cc=ast@kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=quentin.monnet@netronome.com \
--cc=sdf@google.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).