From: Peter Zijlstra <peterz@infradead.org>
To: David Miller <davem@davemloft.net>
Cc: ast@fb.com, mingo@kernel.org, rostedt@goodmis.org,
wangnan0@huawei.com, daniel@iogearbox.net,
brendan.d.gregg@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] bpf_get_stackid() and stack_trace map
Date: Thu, 25 Feb 2016 15:24:54 +0100 [thread overview]
Message-ID: <20160225142454.GO6357@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160220.002505.2066795907514539303.davem@davemloft.net>
On Sat, Feb 20, 2016 at 12:25:05AM -0500, David Miller wrote:
> From: Alexei Starovoitov <ast@fb.com>
> Date: Wed, 17 Feb 2016 19:58:56 -0800
>
> > This patch set introduces new map type to store stack traces and
> > corresponding bpf_get_stackid() helper.
> ...
>
> Series applied, thanks Alexei.
David, please do not apply perf patches without an ACK from me or mingo.
next prev parent reply other threads:[~2016-02-25 14:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 3:58 Alexei Starovoitov
2016-02-18 3:58 ` [PATCH net-next 1/3] perf: generalize perf_callchain Alexei Starovoitov
2016-02-25 14:18 ` Peter Zijlstra
2016-02-25 16:37 ` Alexei Starovoitov
2016-02-25 16:45 ` Peter Zijlstra
2016-02-25 16:48 ` Peter Zijlstra
2016-02-25 16:47 ` Peter Zijlstra
2016-02-25 17:27 ` Alexei Starovoitov
2016-02-18 3:58 ` [PATCH net-next 2/3] bpf: introduce BPF_MAP_TYPE_STACK_TRACE Alexei Starovoitov
2016-02-25 14:23 ` Peter Zijlstra
2016-02-25 16:42 ` Alexei Starovoitov
2016-02-25 16:50 ` Peter Zijlstra
2016-02-18 3:58 ` [PATCH net-next 3/3] samples/bpf: offwaketime example Alexei Starovoitov
2016-02-20 5:25 ` [PATCH net-next 0/3] bpf_get_stackid() and stack_trace map David Miller
2016-02-25 14:24 ` Peter Zijlstra [this message]
2016-02-25 16:44 ` 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=20160225142454.GO6357@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ast@fb.com \
--cc=brendan.d.gregg@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=wangnan0@huawei.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
all inboxes | Powered by JetHome®