[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CE59F3F.3080407@trash.net>
Date: Thu, 18 Nov 2010 22:48:47 +0100
From: Patrick McHardy <kaber@...sh.net>
To: David Miller <davem@...emloft.net>
CC: randy.dunlap@...cle.com, justinmattock@...il.com,
eric.dumazet@...il.com, linux-net@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
horms@...ge.net.au, netfilter-devel@...r.kernel.org
Subject: Re: error while building the kernel Mainline
Am 18.11.2010 22:15, schrieb David Miller:
> From: David Miller <davem@...emloft.net>
> Date: Thu, 18 Nov 2010 13:10:04 -0800 (PST)
>
>> From: Randy Dunlap <randy.dunlap@...cle.com>
>> Date: Thu, 18 Nov 2010 13:03:18 -0800
>>
>>> On Thu, 18 Nov 2010 12:54:51 -0800 (PST) David Miller wrote:
>>>
>>>> From: Patrick McHardy <kaber@...sh.net>
>>>> Date: Thu, 18 Nov 2010 21:32:11 +0100
>>>>
>>>>> Thanks for testing. Dave, please apply directly, thanks!
>>>
>>> Dave,
>>>
>>> This patch does not fix the config/build error that I posted for linux-next.
>>
>> And it has bugs, now when NF_CONNTRACT is set to "m" IPVS isn't offered
>> at all.
>>
>> So I'm reverting.
>
> Ignore this, I was looking for "*_IPVS" in the config instead of
> "*_IP_VS" for some stupid reason.
I always make the same mistake :)
> Patch is sane and I'll look into Randy's problem when I get a chance.
> :-)
I've already asked the tproxy guys to look into this, it's a
different problem that requires more tproxy knowledge than
have.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists