From: Cong Wang <amwang@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
herbert@gondor.hengli.com.au
Subject: Re: [PATCH net-next 0/4] ipv6: fix the reassembly expire code in nf_conntrack
Date: Tue, 18 Sep 2012 10:47:23 +0800 [thread overview]
Message-ID: <1347936443.14402.15.camel@cr0> (raw)
In-Reply-To: <20120917.223559.1226100441781312938.davem@davemloft.net>
On Mon, 2012-09-17 at 22:35 -0400, David Miller wrote:
> From: Cong Wang <amwang@redhat.com>
> Date: Tue, 18 Sep 2012 10:34:16 +0800
>
> > Actually, the #ifdef CONFIG_IPV6 is not needed at all, as
> > sockstat6_seq_show() is their only caller, which is compiled only when
> > CONFIG_IPV6 is enabled.
>
> "#ifdef CONFIG_IPV6 doesn't work for modular ipv6.
Ah... then this should be the cause of your build failure, as I always
compile IPV6 as builtin.
Sorry for this, my bad. I will remove this #ifdef and resend the whole
patchset.
Thanks!
next prev parent reply other threads:[~2012-09-18 2:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 6:25 [PATCH net-next 0/4] ipv6: fix the reassembly expire code in nf_conntrack Cong Wang
2012-09-13 6:25 ` [PATCH 1/4] ipv6: add a new namespace for nf_conntrack_reasm Cong Wang
2012-09-13 6:25 ` [PATCH 2/4] ipv6: unify conntrack reassembly expire code with standard one Cong Wang
2012-09-13 6:25 ` [PATCH 3/4] ipv6: make ip6_frag_nqueues() and ip6_frag_mem() static inline Cong Wang
2012-09-13 6:25 ` [PATCH 4/4] ipv6: unify fragment thresh handling code Cong Wang
2012-09-17 3:13 ` [PATCH net-next 0/4] ipv6: fix the reassembly expire code in nf_conntrack Cong Wang
2012-09-17 16:54 ` David Miller
2012-09-17 16:59 ` David Miller
2012-09-18 2:34 ` Cong Wang
2012-09-18 2:35 ` David Miller
2012-09-18 2:47 ` Cong Wang [this message]
2012-09-18 2:53 ` David Miller
2012-09-18 3:04 ` Cong Wang
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=1347936443.14402.15.camel@cr0 \
--to=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=netdev@vger.kernel.org \
--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 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.