From: Tom Tromey <tom@tromey.com>
To: Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [pushed] Fix aarch64-linux-hw-point.c build problem
Date: Wed, 24 Feb 2021 13:52:00 -0700 [thread overview]
Message-ID: <87ft1lyyrz.fsf@tromey.com> (raw)
In-Reply-To: <20210224195945.2135883-1-kevinb@redhat.com> (Kevin Buettner via Gdb-patches's message of "Wed, 24 Feb 2021 12:59:45 -0700")
>>>>> "Kevin" == Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org> writes:
Kevin> gdb/ChangeLog:
Kevin> * nat/aarch64-linux-hw-point.c: Include <asm/ptrace.h> after
Kevin> <sys/ptrace.h>.
This seems reasonable, but a comment saying that the order matters might
be helpful later on.
Tom
next prev parent reply other threads:[~2021-02-24 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 19:59 Kevin Buettner via Gdb-patches
2021-02-24 20:52 ` Tom Tromey [this message]
2021-02-24 21:52 ` Kevin Buettner via Gdb-patches
2021-02-24 23:22 ` Christian Biesinger via Gdb-patches
2021-02-25 22:49 ` Kevin Buettner via Gdb-patches
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=87ft1lyyrz.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.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