From: Alexei Starovoitov <ast@plumgrid.com>
To: Daniel Borkmann <daniel@iogearbox.net>, davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] ebpf: misc core cleanup
Date: Fri, 29 May 2015 16:25:08 -0700 [thread overview]
Message-ID: <5568F554.2040603@plumgrid.com> (raw)
In-Reply-To: <331333f9ad9f3317ebf128ee90eb32e64404029e.1432912637.git.daniel@iogearbox.net>
On 5/29/15 2:23 PM, Daniel Borkmann wrote:
> Besides others, move bpf_tail_call_proto to the remaining definitions
> of other protos, improve comments a bit (i.e. remove some obvious ones,
> where the code is already self-documenting, add objectives for others),
> simplify bpf_prog_array_compatible() a bit.
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
bpf_check_tail_call() cleanup is nice. The rest won't hurt ;)
Acked-by: Alexei Starovoitov <ast@plumgrid.com>
next prev parent reply other threads:[~2015-05-29 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 21:23 [PATCH net-next 0/2] bpf misc update Daniel Borkmann
2015-05-29 21:23 ` [PATCH net-next 1/2] ebpf: allow bpf_ktime_get_ns_proto also for networking Daniel Borkmann
2015-06-01 4:44 ` David Miller
2015-05-29 21:23 ` [PATCH net-next 2/2] ebpf: misc core cleanup Daniel Borkmann
2015-05-29 23:25 ` Alexei Starovoitov [this message]
2015-06-01 4:45 ` 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=5568F554.2040603@plumgrid.com \
--to=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--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).