From: Daniel Borkmann <daniel@iogearbox.net>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: davem@davemloft.net, ast@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH net-next 1/3] trace: add variant without spacing in trace_print_hex_seq
Date: Thu, 26 Jan 2017 21:40:55 +0100 [thread overview]
Message-ID: <588A5ED7.4060001@iogearbox.net> (raw)
In-Reply-To: <20170126195306.GD17504@kernel.org>
On 01/26/2017 08:53 PM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Jan 25, 2017 at 02:28:16AM +0100, Daniel Borkmann escreveu:
>> For upcoming tracepoint support for BPF, we want to dump the program's
>> tag. Format should be similar to __print_hex(), but without spacing.
>> Add a __print_hex_str() variant for exactly that purpose that reuses
>> trace_print_hex_seq().
>
> Steven should be back to his side of the wall soon, will wait for his
> Ack, ok?
Ok, seems this set got applied already to net-next in the meantime, so
if there are any objections on this, I will follow up with a patch of
course.
Thanks,
Daniel
> - Arnaldo
next prev parent reply other threads:[~2017-01-26 20:41 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 [this message]
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 ` [PATCH net-next 0/3] BPF tracepoints 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=588A5ED7.4060001@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.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