From: Ralf Baechle <ralf@oss.sgi.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: linux-mips@oss.sgi.com, config-patches@gnu.org
Subject: Re: PATCH: Handle Linux/mips (Re: Why is byteorder removed from /proc/cpuinfo?)
Date: Thu, 6 Dec 2001 16:41:53 -0200 [thread overview]
Message-ID: <20011206164153.E8002@dea.linux-mips.net> (raw)
In-Reply-To: <20011206103605.A7366@lucon.org>; from hjl@lucon.org on Thu, Dec 06, 2001 at 10:36:05AM -0800
On Thu, Dec 06, 2001 at 10:36:05AM -0800, H . J . Lu wrote:
> How about this patch?
Looks good to me except that checking for __MIPSE[LB]__ should be
sufficient. Anything that doesn't provide these two symbols wouldn't
have the chance of a snowball in hell to work.
Ralf
next prev parent reply other threads:[~2001-12-06 19:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 17:35 Why is byteorder removed from /proc/cpuinfo? H . J . Lu
2001-12-06 17:53 ` H . J . Lu
2001-12-06 17:57 ` Ralf Baechle
2001-12-06 18:36 ` PATCH: Handle Linux/mips (Re: Why is byteorder removed from /proc/cpuinfo?) H . J . Lu
2001-12-06 18:41 ` Ralf Baechle [this message]
2001-12-06 18:51 ` H . J . Lu
2001-12-06 19:16 ` Ralf Baechle
2001-12-10 7:23 ` Ben Elliston
2001-12-10 9:42 ` Ben Elliston
2001-12-10 14:21 ` Daniel Jacobowitz
2001-12-10 23:34 ` Ben Elliston
2001-12-10 23:34 ` Ben Elliston
2001-12-11 0:20 ` H . J . Lu
2001-12-11 0:23 ` Ben Elliston
2001-12-11 0:28 ` H . J . Lu
2001-12-10 18:28 ` Ralf Baechle
2001-12-10 20:24 ` Maciej W. Rozycki
2001-12-10 23:40 ` Ben Elliston
2001-12-10 23:40 ` Ben Elliston
2001-12-11 0:04 ` Maciej W. Rozycki
2001-12-11 13:30 ` Ralf Baechle
2001-12-11 23:11 ` Daniel Jacobowitz
2001-12-12 8:07 ` Ben Elliston
2001-12-10 18:40 ` Why is byteorder removed from /proc/cpuinfo? Dominic Sweetman
2001-12-10 19:06 ` Ralf Baechle
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=20011206164153.E8002@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=config-patches@gnu.org \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.sgi.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