From: Gary Benson <gbenson@redhat.com>
To: Will Newton <will.newton@linaro.org>
Cc: "Bin.Cheng" <amker.cheng@gmail.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH]Fix aarch64 native build issue caused by use of LONGEST
Date: Wed, 27 Aug 2014 08:46:00 -0000 [thread overview]
Message-ID: <20140827084638.GA4533@blade.nx> (raw)
In-Reply-To: <CANu=DmjYhc6tHUyLy=jkuug8WMiyqRmJL+Pq08sRzGzvZPwKQA@mail.gmail.com>
Will Newton wrote:
> On 21 August 2014 09:32, Bin.Cheng <amker.cheng@gmail.com> wrote:
> > Recent gdb code refactor changes LONGEST from a macro to a typedef,
> > thus the use of it in aarch64-linux-nat.c is no longer valid.
> >
> > This patch fixes the build failure which is obvious. Is it OK?
> >
> > 2014-08-21 Bin Cheng <bin.cheng@arm.com>
> >
> > * aarch64-linux-nat.c (dr_changed_t): Change the type from
> > unsigned LONGEST to ULONGEST.
>
> I pushed this as obvious given that Marcus is not around.
Bin, Will, thanks for fixing this.
Cheers,
Gary
--
http://gbenson.net/
prev parent reply other threads:[~2014-08-27 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 8:32 Bin.Cheng
2014-08-21 8:40 ` Will Newton
2014-08-27 8:46 ` Gary Benson [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=20140827084638.GA4533@blade.nx \
--to=gbenson@redhat.com \
--cc=amker.cheng@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=will.newton@linaro.org \
/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