From: Tamar Christina <Tamar.Christina@arm.com>
To: Tamar Christina <Tamar.Christina@arm.com>,
"nickc@redhat.com" <nickc@redhat.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Cc: nd <nd@arm.com>, Richard Earnshaw <Richard.Earnshaw@arm.com>,
"Marcus Shawcroft" <Marcus.Shawcroft@arm.com>
Subject: RE: [PATCH][binutils][AArch64] Fix debug trace build for AArch64.
Date: Tue, 15 May 2018 16:49:00 -0000 [thread overview]
Message-ID: <HE1PR08MB0540992C213A14DFF5B0FD18FF930@HE1PR08MB0540.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <DB6PR0802MB250455D8E07E90CD1B8E9562FFBB0@DB6PR0802MB2504.eurprd08.prod.outlook.com>
Hi Nick,
I hadn't noticed that the binutils 2.28 branch and the gdb branch are different.
Permission to backport this to the gdb-8.0-branch as well?
The patch is https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=957f6b39cab6cac0e4c54e650c7f75109544ac1d
Thanks,
Tamar
> -----Original Message-----
> From: binutils-owner@sourceware.org <binutils-owner@sourceware.org>
> On Behalf Of Tamar Christina
> Sent: Thursday, April 5, 2018 15:28
> To: nickc@redhat.com; binutils@sourceware.org
> Cc: nd <nd@arm.com>; Richard Earnshaw <Richard.Earnshaw@arm.com>;
> Marcus Shawcroft <Marcus.Shawcroft@arm.com>
> Subject: RE: [PATCH][binutils][AArch64] Fix debug trace build for AArch64.
>
> Hi Nick,
>
> Thanks!
>
> Cheers,
> Tamar
>
> > -----Original Message-----
> > From: Nick Clifton <nickc@redhat.com>
> > Sent: Thursday, April 5, 2018 14:19
> > To: Tamar Christina <Tamar.Christina@arm.com>; binutils@sourceware.org
> > Cc: nd <nd@arm.com>; Richard Earnshaw <Richard.Earnshaw@arm.com>;
> > Marcus Shawcroft <Marcus.Shawcroft@arm.com>
> > Subject: Re: [PATCH][binutils][AArch64] Fix debug trace build for AArch64.
> >
> > Hi Tamar,
> >
> > > Ping
> >
> > Sorry - I missed this one.
> >
> > >> I'd like to also backport this to binutils 2.28 to fix the debugging build
> there.
> > >>
> > >> Ok for binutils 2.28 branch?
> >
> > Yes.
> >
> > Cheers
> > Nick
next prev parent reply other threads:[~2018-05-15 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 9:42 Tamar Christina
2017-04-24 10:57 ` Nick Clifton
2018-03-12 11:15 ` Tamar Christina
2018-04-05 10:14 ` Tamar Christina
2018-04-05 13:19 ` Nick Clifton
2018-04-05 14:28 ` Tamar Christina
2018-05-15 16:49 ` Tamar Christina [this message]
2018-05-15 16:51 ` Nick Clifton
2018-05-15 16:53 ` Tamar Christina
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=HE1PR08MB0540992C213A14DFF5B0FD18FF930@HE1PR08MB0540.eurprd08.prod.outlook.com \
--to=tamar.christina@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sourceware.org \
--cc=nd@arm.com \
--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).