public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@freebsd.org>, gdb-patches@sourceware.org
Cc: binutils@sourceware.org
Subject: Re: [PATCH v2 0/4] Initial support for FreeBSD/arm in GDB
Date: Wed, 11 Oct 2017 11:14:00 -0000	[thread overview]
Message-ID: <7e4549c3-4ef3-fef8-769e-efdf0e3c3a6f@redhat.com> (raw)
In-Reply-To: <2102789.4VvdLC0lsm@ralph.baldwin.cx>

On 09/29/2017 06:45 PM, John Baldwin wrote:

> Ping?
> 
> Alan Modra has reviewed the binutils bits, and Eli signed off on the NEWS
> change in V1.
> 

Sorry, missed that there was a v2.  In any case, same comment apply,
and the GDB changes look good to me.

I didn't mention explicitly, but just in case the configure.tgt
hunk still applies / builds as is: please be sure to update the
gdb/configure.tgt changes to follow the recent change that
split the cpu and os objects to separate switches.

Thanks,
Pedro Alves

  reply	other threads:[~2017-10-11 11:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 22:58 John Baldwin
2017-09-22 22:58 ` [PATCH v2 2/4] Handle the NT_ARM_VFP core dump note on FreeBSD John Baldwin
2017-09-22 22:58 ` [PATCH v2 3/4] Add FreeBSD/arm architecture John Baldwin
2017-09-22 22:58 ` [PATCH v2 1/4] Handle FreeBSD-specific AT_EHDRFLAGS and AT_HWCAP auxiliary vector types John Baldwin
2017-09-22 23:07 ` [PATCH v2 4/4] Add native target for FreeBSD/arm John Baldwin
2017-09-24 23:49 ` [PATCH v2 0/4] Initial support for FreeBSD/arm in GDB Alan Modra
2017-09-29 17:46 ` John Baldwin
2017-10-11 11:14   ` Pedro Alves [this message]
2017-10-11 17:07     ` John Baldwin

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=7e4549c3-4ef3-fef8-769e-efdf0e3c3a6f@redhat.com \
    --to=palves@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@freebsd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).