From: amol pise <amolpise15@gmail.com>
To: ramrad01@arm.com
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: Cortex-A15 vfnma/vfnms test patch
Date: Mon, 28 Jan 2013 14:03:00 -0000 [thread overview]
Message-ID: <CANUf=CC7YQOvA_3pv52Cr6qXJ6AJYq7v0r_j7ZAv257OcJe+gg@mail.gmail.com> (raw)
In-Reply-To: <51065773.1020207@arm.com>
Dear Ramana,
Thank You very much for the changelog and commit of my patch in gcc.
I will follow the steps mentioned by you.
Thank You,
Amol Pise
On Mon, Jan 28, 2013 at 4:18 PM, Ramana Radhakrishnan <ramrad01@arm.com> wrote:
>
>
> [Taking gcc-help off this thread.]
>
> Amol,
>
>
>> I have tested these instruction with GCC and these instructions are
>> generated.
>> Please review and marge this test support patch in gcc main trunk.
>
>
> Thanks for this patch and sorry about the delay in getting around to this.
>
> This is ok and I'll take this under the 10 line rule this time .
>
> If you intend to continue to submit patches to gcc can I ask that you start
> the process for copyright assignments or confirm that you have a copyright
> assignment on file ?
>
> http://gcc.gnu.org/contribute.html#legal
>
> If you don't, send an email to gcc@gcc.gnu.org with a request for copyright
> assignment papers and a maintainer will send you these.
>
> http://gcc.gnu.org/contribute.html in general is a good summary of the
> process related to contributing patches to GCC in general . Please do read
> that and follow up on gcc@gcc.gnu.org if you have any more questions.
>
> And finally don't forget to add a changelog to your patches as documented in
> links from the above mentioned page. Since this is your first time I've
> added the following Changelog entry for your patch and applied it.
>
> regards
> Ramana
>
>
>
> 2013-01-27 Amol Pise <amolpise15@gmail.com>
>
> * gcc.target/arm/neon-vfnms-1.c: New test.
> * gcc.target/arm/neon-vfnma-1.c: New test.
>
>
>
>
next prev parent reply other threads:[~2013-01-28 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 10:03 amol pise
2013-01-22 5:04 ` amol pise
2013-01-25 18:47 ` Mike Stump
2013-01-27 15:27 ` amol pise
2013-01-28 10:48 ` Ramana Radhakrishnan
2013-01-28 14:03 ` amol pise [this message]
2013-01-31 17:30 ` Ramana Radhakrishnan
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='CANUf=CC7YQOvA_3pv52Cr6qXJ6AJYq7v0r_j7ZAv257OcJe+gg@mail.gmail.com' \
--to=amolpise15@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ramrad01@arm.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).