From: Alex Velenko <Alex.Velenko@arm.com>
To: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: [PATCH AArch64_BE 3/4] Big-Endian lane numbering fix
Date: Tue, 21 Jan 2014 19:00:00 -0000 [thread overview]
Message-ID: <52DEC3E4.20202@arm.com> (raw)
In-Reply-To: <CAFqB+Px9EtdccfJawazvLJ-xbXJrRsyOq+WvdtR8-K8GFSr3Xg@mail.gmail.com>
Hi,
Can someone, please, commit this patch as I do not have privileges to
do so.
Kind regards,
Alex Velenko
On 21/01/14 13:32, Marcus Shawcroft wrote:
> On 16 January 2014 11:50, Alex Velenko <Alex.Velenko@arm.com> wrote:
>> Hi,
>>
>> This patch by James Greenhalgh fixes "by-lane" patterns broken by
>> previous patches.
>>
>>
>> Regression tested on aarch64-none-elf and aarch64_be-none-elf
>> with no unexpected issues.
>>
>> OK?
>>
>
> OK /Marcus
>
prev parent reply other threads:[~2014-01-21 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 11:50 Alex Velenko
2014-01-21 13:32 ` Marcus Shawcroft
2014-01-21 19:00 ` Alex Velenko [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=52DEC3E4.20202@arm.com \
--to=alex.velenko@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=marcus.shawcroft@gmail.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).