From: "Justin P. Mattock" <justinmattock@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: eric.dumazet@gmail.com, linux-net@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
horms@verge.net.au, netfilter-devel@vger.kernel.org,
kaber@trash.net
Subject: Re: error while building the kernel Mainline
Date: Thu, 18 Nov 2010 10:13:24 -0800 [thread overview]
Message-ID: <4CE56CC4.4020107@gmail.com> (raw)
In-Reply-To: <20101118.095046.28818361.davem@davemloft.net>
On 11/18/2010 09:50 AM, David Miller wrote:
> From: Eric Dumazet<eric.dumazet@gmail.com>
> Date: Thu, 18 Nov 2010 18:48:17 +0100
>
>> Let me guess...
>>
>> net/netfilter/nf_conntrack_core is compiled as a module, and ip_vs
>> statically (in vmlinux) ?
>>
>> CONFIG_NF_CONNTRACK=m
>> CONFIG_IP_VS=y
>>
>> We probably need some Kconfig magic ;)
>
> Randy Dunlap made a similar report today with a sample .config
> that triggers the problem.
>
> I'll look into it after lunch.
>
alright..
Justin P. Mattock
next prev parent reply other threads:[~2010-11-18 18:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikToBjx-4go9mAFCcnTQ5X4Su+57ODoY9C5y_7f@mail.gmail.com>
[not found] ` <1290093135.2781.167.camel@edumazet-laptop>
[not found] ` <4CE561A2.2020600@gmail.com>
2010-11-18 17:48 ` error while building the kernel Mainline Eric Dumazet
2010-11-18 17:50 ` David Miller
2010-11-18 18:12 ` Patrick McHardy
2010-11-18 18:13 ` Justin P. Mattock [this message]
2010-11-18 18:20 ` Patrick McHardy
2010-11-18 18:28 ` Justin P. Mattock
2010-11-18 19:18 ` Justin P. Mattock
2010-11-18 20:32 ` Patrick McHardy
2010-11-18 20:54 ` David Miller
2010-11-18 21:03 ` Randy Dunlap
2010-11-18 21:10 ` David Miller
2010-11-18 21:15 ` David Miller
2010-11-18 21:48 ` Patrick McHardy
2010-11-18 23:48 ` Justin P. Mattock
2010-11-19 0:20 ` Simon Horman
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=4CE56CC4.4020107@gmail.com \
--to=justinmattock@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=horms@verge.net.au \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--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 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).