Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266030AbUAUSnx (ORCPT ); Wed, 21 Jan 2004 13:43:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266032AbUAUSnn (ORCPT ); Wed, 21 Jan 2004 13:43:43 -0500 Received: from palrel13.hp.com ([156.153.255.238]:39396 "EHLO palrel13.hp.com") by vger.kernel.org with ESMTP id S266030AbUAUSnW (ORCPT ); Wed, 21 Jan 2004 13:43:22 -0500 From: David Mosberger MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16398.51269.149031.241526@napali.hpl.hp.com> Date: Wed, 21 Jan 2004 10:43:17 -0800 To: Jes Sorensen Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org, Paul Mackerras Subject: Re: [patch] 2.6.1-mm5 compile do not use shared extable code for ia64 In-Reply-To: References: X-Mailer: VM 7.17 under Emacs 21.3.1 Reply-To: davidm@hpl.hp.com X-URL: http://www.hpl.hp.com/personal/David_Mosberger/ Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 835 Lines: 20 >>>>> On Tue, 20 Jan 2004 07:23:49 -0500, Jes Sorensen said: Jes> Hi, Jes> The new sort_extable and shares search_extable code doesn't work on Jes> ia64. I have introduced two new #defines that archs can define to avoid Jes> the common code being built. ARCH_HAS_SEARCH_EXTABLE and Jes> ARCH_HAS_SORT_EXTABLE. Jes> With this patch, 2.6.1-mm5 builds again on ia64. What's this about? Isn't the only reason this doesn't work because the "insn" member is called "addr" on ia64? If so, surely it would make more sense to do a little renaming? --david - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/