public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jes Sorensen <jes@trained-monkey.org>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	paulus@samba.org
Subject: Re: [patch] 2.6.1-mm5 compile do not use shared extable code for
Date: Tue, 20 Jan 2004 17:00:04 +0000	[thread overview]
Message-ID: <20040120090004.48995f2a.akpm@osdl.org> (raw)
In-Reply-To: <E1Aiuv7-0001cS-00@jaguar.mkp.net>

Jes Sorensen <jes@trained-monkey.org> wrote:
>
> The new sort_extable and shares search_extable code doesn't work on
>  ia64.

hm, OK.  It would be nice if ia64 could use the generic code at some stage,
of course.

One wonders why the linker dragged lib/extable.c in at all.  Or does it fail at
compile time?



  reply	other threads:[~2004-01-20 17:00 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 ` Andrew Morton [this message]
2004-01-24  3:00   ` [patch] 2.6.1-mm5 compile do not use shared extable code for 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 ` [patch] 2.6.1-mm5 compile do not use shared extable code for ia64 David Mosberger

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=20040120090004.48995f2a.akpm@osdl.org \
    --to=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