[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F1AC8F6.1060703@parallels.com>
Date: Sat, 21 Jan 2012 18:17:26 +0400
From: Glauber Costa <glommer@...allels.com>
To: David Miller <davem@...emloft.net>
CC: <linux-kernel@...r.kernel.org>, <kamezawa.hiroyu@...fujitsu.com>,
<netdev@...r.kernel.org>, <eric.dumazet@...il.com>,
<cgroups@...r.kernel.org>
Subject: Re: [PATCH 1/3] net: fix socket memcg build with !CONFIG_NET
On 01/20/2012 11:14 PM, David Miller wrote:
> From: Glauber Costa<glommer@...allels.com>
> Date: Fri, 20 Jan 2012 18:57:14 +0400
>
>> There is still a build bug with the sock memcg code, that triggers
>> with !CONFIG_NET, that survived my series of randconfig builds.
>>
>> Signed-off-by: Glauber Costa<glommer@...allels.com>
>> Reported-by: Randy Dunlap<rdunlap@...otime.net>
>> CC: Hiroyouki Kamezawa<kamezawa.hiroyu@...fujitsu.com>
>
> Why are you undoing the static branch optimization? That was a one of
> the things that made me agree to even putting this code in.
>
> Find a way to fix this without removing the static branch.
>
Dave,
I am not removing the static branch. This is just a macro, that expands
to the static branch when the options are in place, and to 0 if they are
not.
if (0) { } is certainly be removed to the compiler, so the code is out
anyway.
--
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