From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ast@kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] BPF tracepoints
Date: Wed, 25 Jan 2017 13:19:28 -0500 (EST) [thread overview]
Message-ID: <20170125.131928.1293307938933551620.davem@davemloft.net> (raw)
In-Reply-To: <cover.1485306168.git.daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Wed, 25 Jan 2017 02:28:15 +0100
> This set adds tracepoints to BPF for better introspection and
> debugging. The first two patches are prerequisite for the actual
> third patch that adds the tracepoints. I think the first two are
> small and straight forward enough that they could ideally go via
> net-next, but I'm also open to other suggestions on how to route
> them in case that's not applicable (it would reduce potential
> merge conflicts on BPF side, though). For details, please see
> individual patches.
Looks great, series applied, thanks Daniel.
prev parent reply other threads:[~2017-01-25 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 1:28 [PATCH net-next 0/3] BPF tracepoints Daniel Borkmann
2017-01-25 1:28 ` [PATCH net-next 1/3] trace: add variant without spacing in trace_print_hex_seq Daniel Borkmann
2017-01-26 19:53 ` Arnaldo Carvalho de Melo
2017-01-26 20:40 ` Daniel Borkmann
2017-01-30 20:44 ` Steven Rostedt
2017-02-01 8:10 ` Daniel Borkmann
2017-01-25 1:28 ` [PATCH net-next 2/3] lib, traceevent: add PRINT_HEX_STR variant Daniel Borkmann
2017-01-30 19:01 ` Steven Rostedt
2017-01-25 1:28 ` [PATCH net-next 3/3] bpf: add initial bpf tracepoints Daniel Borkmann
2017-01-25 18:19 ` David Miller [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=20170125.131928.1293307938933551620.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).