From: "David S. Miller" <davem@redhat.com>
To: rth@cygnus.com
Cc: jj@sunsite.ms.mff.cuni.cz, binutils@sourceware.cygnus.com
Subject: Re: [PATCH] Important gas fixes on sparc
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <199906071804.LAA07283@pizda.davem.net> (raw)
In-Reply-To: <19990607105455.B8485@cygnus.com>
Date: Mon, 7 Jun 1999 10:54:55 -0700
From: Richard Henderson <rth@cygnus.com>
You may want to hack this in your local tree to emit a warning for
R_SPARC_22. Red Hat 6 was delayed on Sparc because of this change.
So there's some amount of assembly code out there that's got this
wrong.
This was fixed, at least in the kernel sources, as soon as I became
aware of hjl's fixes.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Jakub Jelinek
1999-07-01 0:00 ` David S. Miller
1999-07-01 0:00 ` Doug Evans
1999-07-01 0:00 ` Jakub Jelinek
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` David S. Miller [this message]
1999-07-01 0:00 ` Richard Henderson
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=199906071804.LAA07283@pizda.davem.net \
--to=davem@redhat.com \
--cc=binutils@sourceware.cygnus.com \
--cc=jj@sunsite.ms.mff.cuni.cz \
--cc=rth@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).