From: "Inderpreet Singh Baweja" <Inderpreet.Baweja@noida.hcltech.com>
To: "Ben Elliston" <bje+dated+1105761237.fa52ed@air.net.au>,
<config-patches@gnu.org>
Cc: <binutils@sources.redhat.com>
Subject: RE: binutils patch for maxq target
Date: Mon, 10 Jan 2005 05:21:00 -0000 [thread overview]
Message-ID: <33BC33A9E76474479B76AD0DE8A16972015C99@exch-ntd.nec.noida.hcltech.com> (raw)
Hi Ben,
I am sending the patch for the config.sub.
I have attached the Changelog.
Please commit this.
------------------------ ChangeLog ----------------------------
2004-12-17 Inderpreet Singh <inderpreetb@noida.hcltech.com>
* config.sub: Add new target maxq.
**************** PATCH ************************************
Index: config.sub
===================================================================
RCS file: /cvs/src/src/config.sub,v
retrieving revision 1.49
diff -c -3 -p -r1.49 config.sub
*** config.sub 16 Nov 2004 01:18:39 -0000 1.49
--- config.sub 16 Nov 2004 14:27:58 -0000
*************** case $basic_machine in
*** 237,243 ****
| h8300 | h8500 | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] |
hppa64 \
| i370 | i860 | i960 | ia64 \
| ip2k | iq2000 \
! | m32r | m32rle | m68000 | m68k | m88k | mcore \
| mips | mipsbe | mipseb | mipsel | mipsle \
| mips16 \
| mips64 | mips64el \
--- 237,243 ----
| h8300 | h8500 | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] |
hppa64 \
| i370 | i860 | i960 | ia64 \
| ip2k | iq2000 \
! | m32r | m32rle | m68000 | m68k | m88k | maxq | mcore \
| mips | mipsbe | mipseb | mipsel | mipsle \
| mips16 \
| mips64 | mips64el \
*************** case $basic_machine in
*** 311,317 ****
| m32r-* | m32rle-* \
| m68000-* | m680[012346]0-* | m68360-* | m683?2-* | m68k-* \
| m88110-* | m88k-* | mcore-* \
! | mips-* | mipsbe-* | mipseb-* | mipsel-* | mipsle-* \
| mips16-* \
| mips64-* | mips64el-* \
| mips64vr-* | mips64vrel-* \
--- 311,317 ----
| m32r-* | m32rle-* \
| m68000-* | m680[012346]0-* | m68360-* | m683?2-* | m68k-* \
| m88110-* | m88k-* | mcore-* \
! | maxq-* | mips-* | mipsbe-* | mipseb-* | mipsel-* | mipsle-* \
| mips16-* \
| mips64-* | mips64el-* \
| mips64vr-* | mips64vrel-* \
*************** case $basic_machine in
*** 646,651 ****
--- 646,654 ----
m88k-omron*)
basic_machine=m88k-omron
;;
+ maxq)
+ basic_machine=maxq
+ ;;
magnum | m3230)
basic_machine=mips-mips
os=-sysv
-------------------------------------------------------------------
Thanks,
Inder.
> -----Original Message-----
> From: binutils-owner@sources.redhat.com
> [mailto:binutils-owner@sources.redhat.com] On Behalf Of Ben Elliston
> Sent: Monday, January 10, 2005 9:24 AM
> To: Inderpreet Singh Baweja
> Cc: binutils@sources.redhat.com
> Subject: Re: binutils patch for maxq target
>
> Hi Inderpreet,
>
> I cannot recall receiving a patch from you for config.sub for
> the maxq target. If I have missed it, I'm very sorry.
> Please try re-sending it to config-patches and I will take
> care of it right away.
>
> Cheers, Ben
>
next reply other threads:[~2005-01-10 5:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 5:21 Inderpreet Singh Baweja [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-10 3:54 Ben Elliston
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=33BC33A9E76474479B76AD0DE8A16972015C99@exch-ntd.nec.noida.hcltech.com \
--to=inderpreet.baweja@noida.hcltech.com \
--cc=binutils@sources.redhat.com \
--cc=bje+dated+1105761237.fa52ed@air.net.au \
--cc=config-patches@gnu.org \
/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).