From: Daniel Jacobowitz <drow@false.org>
To: Masaki MURANAKA <monaka@monami-software.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] HR5000 target
Date: Mon, 03 Apr 2006 03:13:00 -0000 [thread overview]
Message-ID: <20060403031347.GA27402@nevyn.them.org> (raw)
In-Reply-To: <BF7ADE54-80FE-4D1A-8A90-FCCF845B7B97@monami-software.com>
On Mon, Apr 03, 2006 at 11:56:05AM +0900, Masaki MURANAKA wrote:
> Hello,
>
> Here is the small patch to support HIREC HR5000 target.
> HR5000 which has MIPS 5kf is used for the aerospace.
>
> ----
> 2006-04-03 Masaki MURANAKA <monaka@monami-software.com>
>
> * config.sub: Add cases for the HIREC hr5000
> (which has MIPS 5kf core).
Two things:
- Patches to config.sub should not be sent here. See the top-level
MAINTAINERS file; I believe it's config-patches@gnu.org.
- Why does this need its own target triplet? Can't you use a normal
mips-elf or mips64-elf toolchain for this target?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-03 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 2:56 Masaki MURANAKA
2006-04-03 3:13 ` Daniel Jacobowitz [this message]
2006-04-03 3:35 ` Masaki MURANAKA
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=20060403031347.GA27402@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=monaka@monami-software.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