From: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
To: "nickc@redhat.com" <nickc@redhat.com>,
Przemyslaw Wirkus <Przemyslaw.Wirkus@arm.com>,
Binutils <binutils@sourceware.org>
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>
Subject: RE: [GAS][AArch64] Add support for Cortex-A78 and Cortex-A78AE
Date: Wed, 30 Sep 2020 14:05:34 +0000 [thread overview]
Message-ID: <DB7PR08MB300223C8E92D83B2F527D47B93330@DB7PR08MB3002.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <fdb42b06-d09d-d598-de4c-491857eccd98@redhat.com>
Hi Nick,
> -----Original Message-----
> From: Binutils <binutils-bounces@sourceware.org> On Behalf Of Nick Clifton
> via Binutils
> Sent: 30 September 2020 14:53
> To: Przemyslaw Wirkus <Przemyslaw.Wirkus@arm.com>;
> binutils@sourceware.org
> Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>; Marcus Shawcroft
> <Marcus.Shawcroft@arm.com>; Ramana Radhakrishnan
> <Ramana.Radhakrishnan@arm.com>
> Subject: Re: [GAS][AArch64] Add support for Cortex-A78 and Cortex-A78AE
>
> Hi Przemyslaw,
>
> > 2020-09-30 Przemyslaw Wirkus <przemyslaw.wirkus@arm.com>
> >
> > * config/tc-aarch64.c: Add Cortex-A78 and Cortex-A78AE cores.
> > * doc/c-aarch64.texi: Update docs.
> > * NEWS: Update news.
>
> Approved and applied.
Would it be possible for Przemyslaw to apply for write-after-approval commit access to Binutils to push his own patches in the future?
Przemyslaw, I believe you already have an account on sourceware.org for GCC?
Thanks,
Kyrill
>
> Cheers
> Nick
>
next prev parent reply other threads:[~2020-09-30 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 11:00 Przemyslaw Wirkus
2020-09-30 13:53 ` Nick Clifton
2020-09-30 14:05 ` Kyrylo Tkachov [this message]
2020-09-30 18:05 ` Przemyslaw Wirkus
2020-10-02 11:22 ` Nick Clifton
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=DB7PR08MB300223C8E92D83B2F527D47B93330@DB7PR08MB3002.eurprd08.prod.outlook.com \
--to=kyrylo.tkachov@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Przemyslaw.Wirkus@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).