Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Eric Christopher <echristo@redhat.com>, mark@codesourcery.com
Cc: gcc-patches@gcc.gnu.org, linux-mips@oss.sgi.com
Subject: Re: PATCH: Clean up Linux/mips.
Date: Wed, 8 Aug 2001 07:35:09 -0700	[thread overview]
Message-ID: <20010808073509.A26983@lucon.org> (raw)
In-Reply-To: <997280370.1290.43.camel@ghostwheel.cygnus.com>; from echristo@redhat.com on Wed, Aug 08, 2001 at 03:19:28PM +0100

On Wed, Aug 08, 2001 at 03:19:28PM +0100, Eric Christopher wrote:
> 
> > 
> > No. I will let their maintainers decide what to do. Personally, I think they
> > should use it :-(. But it may require additional changes.
> > 
> 
> *sigh* That'd be me then.  Ok.  Make sure your changelog entry states
> that mipsel*-linux-* is the only one using it then.
> 

I changed it to

        * config/mips/little.h: New. Generic little endian mips
        targets. Only mips*-*-linux* is converted to use it so far. 

BTW, let me know if it is ok to check in. Also, I'd like to check it
into gcc 3.0.1 if it is approved for the trunk.

Thanks.


H.J.

  reply	other threads:[~2001-08-08 14:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 15:42 PATCH: Clean up Linux/mips H . J . Lu
2001-08-08 13:51 ` Eric Christopher
2001-08-08 14:17   ` H . J . Lu
2001-08-08 14:19     ` Eric Christopher
2001-08-08 14:35       ` H . J . Lu [this message]
2001-08-08 14:38         ` Eric Christopher
2001-08-08 14:47           ` H . J . Lu
2001-08-08 15:04           ` Mark Mitchell
2001-08-08 15:08             ` H . J . Lu
2001-08-08 15:39               ` Mark Mitchell
2001-08-08 15:45                 ` H . J . Lu
2001-08-08 15:52                   ` Mark Mitchell
2001-08-08 16:09                     ` H . J . Lu
2001-08-08 16:12                       ` Mark Mitchell

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=20010808073509.A26983@lucon.org \
    --to=hjl@lucon.org \
    --cc=echristo@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=mark@codesourcery.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