From: Varka Bhadram <varkabhadram@gmail.com>
To: Alexei Starovoitov <ast@plumgrid.com>,
"David S. Miller" <davem@davemloft.net>
Cc: Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] net: filter: split filter.c into two files
Date: Wed, 23 Jul 2014 11:41:58 +0530 [thread overview]
Message-ID: <53CF522E.9090408@gmail.com> (raw)
In-Reply-To: <1406095319-3627-2-git-send-email-ast@plumgrid.com>
On 07/23/2014 11:31 AM, Alexei Starovoitov wrote:
> BPF is used in several kernel components. This split creates logical boundary
> between generic eBPF core and the rest
>
> kernel/bpf/core.c: eBPF interpreter
>
> net/core/filter.c: classic->eBPF converter, classic verifiers, socket filters
>
> This patch only moves functions.
If we are moving the code also its good to do cleanup.
Run checkpatch.pl on this...
--
Regards,
Varka Bhadram.
next prev parent reply other threads:[~2014-07-23 6:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 6:01 [PATCH net-next 0/2] net: filter: split eBPF interpreter out of core networking Alexei Starovoitov
2014-07-23 6:01 ` [PATCH net-next 1/2] net: filter: split filter.c into two files Alexei Starovoitov
2014-07-23 6:11 ` Varka Bhadram [this message]
2014-07-23 8:26 ` David Laight
2014-07-23 8:54 ` Daniel Borkmann
2014-07-23 16:49 ` Alexei Starovoitov
2014-07-24 23:45 ` Valdis.Kletnieks
2014-07-24 23:58 ` Alexei Starovoitov
2014-07-25 0:48 ` Valdis.Kletnieks
2014-07-23 6:01 ` [PATCH net-next 2/2] bpf: update MAINTAINERS entry Alexei Starovoitov
2014-07-24 4:08 ` [PATCH net-next 0/2] net: filter: split eBPF interpreter out of core networking David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-06-01 1:42 [PATCH net-next 0/2] split BPF " Alexei Starovoitov
2014-06-01 1:42 ` [PATCH net-next 1/2] net: filter: split filter.c into two files Alexei Starovoitov
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=53CF522E.9090408@gmail.com \
--to=varkabhadram@gmail.com \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.