Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: pa reload problem
Date: Mon, 4 Dec 2000 18:41:25 +0000	[thread overview]
Message-ID: <20001204184125.L7166@linuxcare.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0012041223530.13095-100000@front.linuxcare.com.au>; from alan@linuxcare.com.au on Mon, Dec 04, 2000 at 12:41:29PM +1100

On Mon, Dec 04, 2000 at 12:41:29PM +1100, Alan Modra wrote:
> I've applied this patch to pehc CVS to fix an hppa64 gcc problem that
> Richard found when compiling modules for the 64-bit kernel.  It's not
> specific to modules, but rather can affect anything requiring stubs to
> call functions, eg. 64-bit userland linked to shared libs.

And it works :-)  I can now insmod sym53c8xx.o on the A500 successfully.

Many thanks,
  Richard

  reply	other threads:[~2000-12-04 18:43 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-01  0:23 [parisc-linux] pa reload problem Alan Modra
2000-12-01  6:12 ` John David Anglin
2000-12-01  7:00   ` Alan Modra
2000-12-02  7:33     ` John David Anglin
2000-12-02  7:48       ` John David Anglin
2000-12-02 23:28         ` John David Anglin
2000-12-05 19:42           ` John David Anglin
2000-12-06 20:41             ` John David Anglin
2000-12-07  0:16               ` Richard Henderson
2000-12-07  0:57                 ` John David Anglin
2000-12-07  1:18                   ` John David Anglin
2000-12-08 22:05                 ` John David Anglin
2000-12-08 23:45                   ` Richard Henderson
2000-12-09  1:07                     ` John David Anglin
2000-12-09  1:39                       ` Richard Henderson
2000-12-09  3:12                         ` John David Anglin
2000-12-09  4:05                         ` Jeffrey A Law
2000-12-09  6:55                           ` Richard Henderson
2000-12-11 17:29                             ` Jeffrey A Law
2000-12-11 18:48                               ` John David Anglin
2000-12-11 23:51                                 ` Alan Modra
2000-12-09  7:52                           ` Alan Modra
2000-12-09  7:55                             ` Richard Henderson
2000-12-09  8:35                               ` Alan Modra
2000-12-09 13:57                                 ` Alan Modra
2000-12-09 18:56                                   ` Richard Henderson
2000-12-09 23:35                                     ` Alan Modra
2000-12-22 17:21                         ` John David Anglin
2000-12-30 19:05                           ` John David Anglin
2001-01-01 23:24                             ` Jeffrey A Law
2000-12-11 21:27                     ` Michael Meissner
2000-12-02 12:35       ` Alan Modra
2000-12-02 19:43         ` Richard Henderson
2000-12-02 23:01           ` John David Anglin
2000-12-03  1:50             ` Richard Henderson
2000-12-03  3:30           ` Alan Modra
2000-12-02 23:08         ` John David Anglin
2000-12-04  1:41         ` Alan Modra
2000-12-04 18:41           ` Richard Hirst [this message]
     [not found] <20001201202613.E7166@linuxcare.com>
2000-12-02  7:15 ` Alan Modra
2000-12-04 18:40   ` Richard Hirst
2000-12-04 22:55     ` Alan Modra
2000-12-04 23:08       ` John David Anglin
2000-12-04 23:59         ` Alan Modra
2000-12-05  0:50           ` John David Anglin
2000-12-05  5:33             ` Alan Modra
     [not found] <no.id>
2000-12-14  0:48 ` John David Anglin
2000-12-14  3:43   ` Jeffrey A Law
2000-12-14 16:40     ` John David Anglin
2000-12-27 20:08       ` Jeffrey A Law
2000-12-28  5:18         ` John David Anglin

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=20001204184125.L7166@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=alan@linuxcare.com.au \
    --cc=parisc-linux@thepuffingroup.com \
    /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