From: David Mosberger <davidm@napali.hpl.hp.com>
To: Jes Sorensen <jes@trained-monkey.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [patch] 2.6.1-mm5 compile do not use shared extable code for ia64
Date: Wed, 21 Jan 2004 18:43:17 +0000 [thread overview]
Message-ID: <16398.51269.149031.241526@napali.hpl.hp.com> (raw)
In-Reply-To: <E1Aiuv7-0001cS-00@jaguar.mkp.net>
>>>>> On Tue, 20 Jan 2004 07:23:49 -0500, Jes Sorensen <jes@trained-monkey.org> 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
prev parent reply other threads:[~2004-01-21 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 12:23 [patch] 2.6.1-mm5 compile do not use shared extable code for ia64 Jes Sorensen
2004-01-20 17:00 ` [patch] 2.6.1-mm5 compile do not use shared extable code for Andrew Morton
2004-01-24 3:00 ` David Mosberger
2004-01-24 10:49 ` Paul Mackerras
2004-01-26 23:33 ` David Mosberger
2004-01-27 8:11 ` [patch] 2.6.1-mm5 compile do not use shared extable code for ia64 Jes Sorensen
2004-01-27 17:39 ` David Mosberger
2004-01-27 8:56 ` [patch] 2.6.1-mm5 compile do not use shared extable code for Paul Mackerras
2004-01-27 16:19 ` David Mosberger
2004-01-27 23:49 ` Paul Mackerras
2004-01-28 6:06 ` David Mosberger
2004-01-27 17:54 ` David Mosberger
2004-01-21 18:43 ` David Mosberger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16398.51269.149031.241526@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=akpm@osdl.org \
--cc=jes@trained-monkey.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox