From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: linux-next: Tree for Jan 25 (net/sock.h, jump_label, memcg) Date: Thu, 26 Jan 2012 13:43:33 -0500 (EST) Message-ID: <20120126.134333.31948964659222759.davem@davemloft.net> References: <20120125141938.c1a9460d56948e1c7b26d3f8@canb.auug.org.au> <4F2052DB.4060602@xenotime.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: rdunlap@xenotime.net, sfr@canb.auug.org.au, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, gleb@redhat.com, netdev@vger.kernel.org, glommer@parallels.com To: geert@linux-m68k.org Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org From: Geert Uytterhoeven Date: Thu, 26 Jan 2012 18:18:28 +0100 > On Wed, Jan 25, 2012 at 20:07, Randy Dunlap wrote: >> back to net/sock.h and jump_label: >> >> (on i386:) >> >> /next/linux-next-20120125/include/net/sock.h:953:2: error: implicit declaration of function 'static_branch' >> /next/linux-next-20120125/include/linux/jump_label.h:43:29: error: conflicting types for 'static_branch' >> >> Full randconfig file is attached. > > Without having to add randomness, also in m68k/allmodconfig, now in Linus' > tree :-( > http://kisskb.ellerman.id.au/kisskb/buildresult/5491860/ Glauber are you actually going to fix this or are you going to ignore this bug report for another couple days?!?! Frankly, I'm so sick and tired of all of these socket mem cgroup regressions, this is way out of control and every "fix" seems to add more build or runtime regressions. Glauber, this has to stabilize soon or I will revert every single one of your changes, and it will take a nuclear war and a multi-month audit of your code to get those changes into the tree again.