From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <4F59BE04.5030509@suse.cz> Date: Fri, 09 Mar 2012 09:23:32 +0100 From: Jiri Slaby MIME-Version: 1.0 To: Willy Tarreau CC: Ben Hutchings , Heiko Carstens , Greg KH , linux-kernel@vger.kernel.org, Andrew Morton , torvalds@linux-foundation.org, stable@vger.kernel.org, lwn@lwn.net, Tony Luck , Jiri Slaby , raven@themaw.net Subject: Re: Build broken on s390 and ia64 [was: Linux 2.6.32.58] References: <20120304180911.GA7336@kroah.com> <4F54A46A.6000305@suse.cz> <20120305120241.GA3627@osiris.boeblingen.de.ibm.com> <4F54B618.1090301@suse.cz> <20120305223338.GE2930@1wt.eu> <1331270953.3022.89.camel@deadeye> <20120309065703.GE25153@1wt.eu> In-Reply-To: <20120309065703.GE25153@1wt.eu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On 03/09/2012 07:57 AM, Willy Tarreau wrote: > Thanks but now I have a doubt, maybe Jiri and Tony can help. In the > commit above, Tony says that CONFIG_COMPAT has been broken for a long > time (2008) and nobody apparently uses it. Still, Jiri got a build > failure because he used CONFIG_COMPAT. So either there are some valid > uses and we should not remove the feature that late in a stable branch, > or Jiri only encountered it upon a make allyesconfig then it might > be safe to remove it. It's a SLE11-SP1 that is using the kernel and has COMPAT on ia64 enabled. I don't know if it is broken or if we provide support for that. If you are sure COMPAT is broken on ia64 even in 2.6.32, feel free to ban COMPAT completely. thanks, -- js suse labs