From: <Andrew_Pinski@PlayStation.Sony.Com>
To: Michael Meissner <meissner@linux.vnet.ibm.com>
Cc: edelsohn@gnu.org, gcc-patches@gcc.gnu.org,
Trevor_Smigiel@PlayStation.Sony.com
Subject: Re: [PATCH] PR target/38025
Date: Wed, 05 Nov 2008 23:39:00 -0000 [thread overview]
Message-ID: <OFAD764200.E06EC53E-ON882574F8.0081CD59-882574F8.0081D492@playstation.sony.com> (raw)
In-Reply-To: <20081105233330.GA1449@hungry-tiger.westford.ibm.com>
Michael Meissner <meissner@linux.vnet.ibm.com> wrote on 11/05/2008
03:33:30 PM:
> I was looking at the spu make check output, and it looks like we need to
update
> the error messages for intrinsics-1.c:
>
> Is this ok to apply?
Yes.
Thanks,
Andrew Pinski
prev parent reply other threads:[~2008-11-05 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 23:34 Michael Meissner
2008-11-05 23:39 ` Andrew_Pinski [this message]
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=OFAD764200.E06EC53E-ON882574F8.0081CD59-882574F8.0081D492@playstation.sony.com \
--to=andrew_pinski@playstation.sony.com \
--cc=Trevor_Smigiel@PlayStation.Sony.com \
--cc=edelsohn@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.vnet.ibm.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).