From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: fw@strlen.de, bernhard.thaler@wvnet.at
Subject: Re: [PATCH nf-next 2/2] netfilter: bridge: split ipv6 code out of the core
Date: Tue, 16 Jun 2015 14:39:45 +0200 [thread overview]
Message-ID: <20150616123945.GA32573@salvia> (raw)
In-Reply-To: <1434458106-32445-2-git-send-email-pablo@netfilter.org>
On Tue, Jun 16, 2015 at 02:35:06PM +0200, Pablo Neira Ayuso wrote:
> Reduce ifdef pollution by moving the IPv6 code into a separated
> br_netfilter_ipv6.c file that is compiled if CONFIG_IPV6 is set.
This patch description is wrong btw, if you confirm this is OK, I'll
replace it by
"Resolve compilation breakage when CONFIG_IPV6 is not set by moving the
IPv6 code into a separated br_netfilter_ipv6.c file."
> Fixes: efb6de9b4ba0 ("netfilter: bridge: forward IPv6 fragmented packets")
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
> @Bernhard: Could you please test this to check if it solves kbuild robot
> problems with CONFIG_IPV6 n, y and m? It would be also good to test this in
> your testbed too to make sure IPv6 things didn't break. Thanks.
>
> I think it should be possible to refactor this a little bit more so other
> remaining IPv6 code specific can go into the file.
prev parent reply other threads:[~2015-06-16 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 12:35 [PATCH nf-next 1/2] netfilter: bridge: rename br_netfilter.c to br_netfilter_hooks.c Pablo Neira Ayuso
2015-06-16 12:35 ` [PATCH nf-next 2/2] netfilter: bridge: split ipv6 code out of the core Pablo Neira Ayuso
2015-06-16 12:39 ` Pablo Neira Ayuso [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=20150616123945.GA32573@salvia \
--to=pablo@netfilter.org \
--cc=bernhard.thaler@wvnet.at \
--cc=fw@strlen.de \
--cc=netfilter-devel@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).