From: Daniel Borkmann <daniel@iogearbox.net>
To: David Miller <davem@davemloft.net>
Cc: ast@plumgrid.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 00/10] eBPF support for cls_bpf
Date: Sun, 01 Mar 2015 10:49:18 +0100 [thread overview]
Message-ID: <54F2E09E.8070302@iogearbox.net> (raw)
In-Reply-To: <20150301.002839.859474631671429798.davem@davemloft.net>
On 03/01/2015 06:28 AM, David Miller wrote:
...
> Daniel please respin this without the arch patches, those should
> go via the various arch maintainer's tree(s).
Okay, will do.
Thanks,
Daniel
prev parent reply other threads:[~2015-03-01 9:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 14:55 [PATCH net-next 00/10] eBPF support for cls_bpf Daniel Borkmann
2015-02-27 14:55 ` [PATCH net-next 01/10] ebpf: remove kernel test stubs Daniel Borkmann
2015-02-27 14:55 ` [PATCH net-next 02/10] ebpf: constify various function pointer structs Daniel Borkmann
2015-02-27 14:55 ` [PATCH net-next 03/10] ebpf: export BPF_PSEUDO_MAP_FD to uapi Daniel Borkmann
2015-02-27 14:55 ` [PATCH net-next 04/10] ebpf: make internal bpf API independent of CONFIG_BPF_SYSCALL ifdefs Daniel Borkmann
2015-02-27 14:55 ` [PATCH net-next 05/10] ebpf: remove CONFIG_BPF_SYSCALL ifdefs in socket filter code Daniel Borkmann
2015-02-27 14:55 ` [PATCH net-next 06/10] ebpf: add sched_cls_type and map it to sk_filter's verifier ops Daniel Borkmann
2015-02-27 14:55 ` [PATCH net-next 07/10] ebpf: move read-only fields to bpf_prog and shrink bpf_prog_aux Daniel Borkmann
2015-02-27 14:55 ` [PATCH net-next 08/10] x86: unexport set_memory_ro and set_memory_rw Daniel Borkmann
2015-02-27 14:55 ` [PATCH net-next 09/10] arm64: " Daniel Borkmann
2015-02-27 18:51 ` Laura Abbott
2015-02-27 19:54 ` Will Deacon
2015-02-27 20:05 ` Daniel Borkmann
2015-03-01 9:52 ` Daniel Borkmann
2015-02-27 14:55 ` [PATCH net-next 10/10] cls_bpf: add initial eBPF support for programmable classifiers Daniel Borkmann
2015-03-01 5:28 ` [PATCH net-next 00/10] eBPF support for cls_bpf David Miller
2015-03-01 9:49 ` Daniel Borkmann [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=54F2E09E.8070302@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@plumgrid.com \
--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).