From: Kazuhiro Inaoka <inaoka.kazuhiro@renesas.com>
To: Ben Elliston <bje@wasabisystems.com>
Cc: cgen@sources.redhat.com
Subject: Re: [patch] change comment to refer to Renesas.
Date: Tue, 10 Jun 2003 05:02:00 -0000 [thread overview]
Message-ID: <003001c32f0d$af6c5a60$2569910a@hoku.renesas.com> (raw)
In-Reply-To: <87r8623gjm.fsf@sashimi.wasabisystems.com>
Hello,
It is important for M32R users and Renesas.
Target M32R was Renesas MCU not Mitsubishi form April 1st 2003.
(Target SH was already changed to refer to Renesas / SuperH.)
Now Mitsubishi has no information of M32R processor.
Infomation site of M32R processor was changed too.
Please change the link page on http://sources.redhat.com/cgen/ to following.
http://www.renesas.com/eng/products/mpumcu/32bit/m32r/index.html
The M32R users will be lost if it is not changed.
We need your help.
Thanks,
Kazuhiro
----- Original Message -----
From: "Ben Elliston" <bje@wasabisystems.com>
To: <cgen@sources.redhat.com>
Sent: Tuesday, June 10, 2003 9:46 AM
Subject: Re: [patch] change comment to refer to Renesas.
> Kazuhiro Inaoka <inaoka.kazuhiro@renesas.com> writes:
>
> > Renesas Technology Corp. is a new semiconductor company, established
> > on April 1st, 2003, as a joint venture between Hitachi, Ltd.(TSE:
> > 6501) and Mitsubishi Electric Corporation(TSE: 6503).
>
> I'm not sure this patch is really necessary. For instance, there will
> be a lot of documentation and other printed material that refers to
> the Mitsubishi M32R. It would be confusing to rename this in
> retrospect and make it hard to find mention of the "Mitsubishi M32R"
> for those who know it as such.
>
> Ben
>
>
next prev parent reply other threads:[~2003-06-10 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 7:54 Kazuhiro Inaoka
2003-06-10 0:46 ` Ben Elliston
2003-06-10 5:02 ` Kazuhiro Inaoka [this message]
2003-06-13 4:03 ` Ben Elliston
2003-06-13 4:40 ` Kazuhiro Inaoka
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='003001c32f0d$af6c5a60$2569910a@hoku.renesas.com' \
--to=inaoka.kazuhiro@renesas.com \
--cc=bje@wasabisystems.com \
--cc=cgen@sources.redhat.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).