From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: "Hurugalawadi, Naveen" <Naveen.Hurugalawadi@cavium.com>,
"Pinski, Andrew" <Andrew.Pinski@cavium.com>
Cc: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>,
James Greenhalgh <James.Greenhalgh@arm.com>, nd <nd@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PING 2] [PATCH] [AArch64] Implement ALU_BRANCH fusion
Date: Fri, 26 May 2017 11:39:00 -0000 [thread overview]
Message-ID: <AM5PR0802MB261092BFF087B633408E4DED83FC0@AM5PR0802MB2610.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CO2PR07MB269491D0C31D71EB9B84349183FC0@CO2PR07MB2694.namprd07.prod.outlook.com>
Hurugalawadi, Naveen <Naveen.Hurugalawadi@cavium.com> wrote:
>
> Please consider this as a personal reminder to review the patch
> at following link and let me know your comments on the same.
>
> https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01333.html
Looks good to me.
Wilco
next prev parent reply other threads:[~2017-05-26 11:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <VI1PR0802MB26218E2C0940948518A0571783210@VI1PR0802MB2621.eurprd08.prod.outlook.com>
2017-03-15 15:20 ` [PATCH][AArch64] " Wilco Dijkstra
2017-03-21 5:37 ` Andrew Pinski
2017-03-27 7:33 ` Hurugalawadi, Naveen
2017-04-25 7:44 ` [PING][PATCH][AArch64] " Hurugalawadi, Naveen
2017-04-25 11:39 ` Wilco Dijkstra
2017-04-26 12:59 ` Hurugalawadi, Naveen
2017-04-26 14:29 ` Wilco Dijkstra
2017-04-27 7:32 ` Hurugalawadi, Naveen
2017-05-11 4:57 ` [PING] [PATCH] [AArch64] " Hurugalawadi, Naveen
2017-05-26 7:14 ` [PING 2] " Hurugalawadi, Naveen
2017-05-26 11:39 ` Wilco Dijkstra [this message]
2017-06-14 10:29 ` [PING 3] " Hurugalawadi, Naveen
2017-06-14 11:37 ` [PING][PATCH][AArch64] " James Greenhalgh
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=AM5PR0802MB261092BFF087B633408E4DED83FC0@AM5PR0802MB2610.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=Andrew.Pinski@cavium.com \
--cc=James.Greenhalgh@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Naveen.Hurugalawadi@cavium.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@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).