From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [RFA v2] Consolidate API of target_supports_multi_process
Date: Thu, 06 Oct 2016 16:37:00 -0000 [thread overview]
Message-ID: <7a62adad-c83a-8887-5474-e27ca1f4d454@redhat.com> (raw)
In-Reply-To: <1475013200-22912-1-git-send-email-sergiodj@redhat.com>
On 09/27/2016 10:53 PM, Sergio Durigan Junior wrote:
> [ Resending with ChangeLog diffs. ]
>
> This simple commit consolidates the API of
> target_supports_multi_process. Since both GDB and gdbserver use the
> same function prototype, all that was needed was to move create this
> prototype on gdb/target/target.h and turn the macros declared on
> gdb/{,gdbserver/}target.h into actual functions.
>
> Regtested (clean pass) on the BuildBot.
OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-10-06 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 21:51 [RFA] " Sergio Durigan Junior
2016-09-27 22:22 ` [RFA v2] " Sergio Durigan Junior
2016-10-06 16:37 ` Pedro Alves [this message]
2016-10-06 21:02 ` Sergio Durigan Junior
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=7a62adad-c83a-8887-5474-e27ca1f4d454@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@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).