From: David Miller <davem@davemloft.net>
To: ast@fb.com
Cc: daniel@iogearbox.net, arb@fb.com, netdev@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH net-next] samples/bpf: fix bpf_perf_event_output prototype
Date: Wed, 10 Aug 2016 23:13:00 -0700 (PDT) [thread overview]
Message-ID: <20160810.231300.570988327885018926.davem@davemloft.net> (raw)
In-Reply-To: <1470847539-2048114-1-git-send-email-ast@fb.com>
From: Alexei Starovoitov <ast@fb.com>
Date: Wed, 10 Aug 2016 09:45:39 -0700
> From: Adam Barth <arb@fb.com>
>
> The commit 555c8a8623a3 ("bpf: avoid stack copy and use skb ctx for event output")
> started using 20 of initially reserved upper 32-bits of 'flags' argument
> in bpf_perf_event_output(). Adjust corresponding prototype in samples/bpf/bpf_helpers.h
>
> Signed-off-by: Adam Barth <arb@fb.com>
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> Acked-by: Daniel Borkmann <daniel@iogearbox.net>
Applied, thanks.
prev parent reply other threads:[~2016-08-11 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 16:45 [PATCH net-next] samples/bpf: fix bpf_perf_event_output prototype Alexei Starovoitov
2016-08-11 6:13 ` 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=20160810.231300.570988327885018926.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arb@fb.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--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).