From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] Share target_wait prototype between GDB and gdbserver
Date: Wed, 31 Aug 2016 10:30:00 -0000 [thread overview]
Message-ID: <4942deb9-426d-856b-decf-22eb80744bb0@redhat.com> (raw)
In-Reply-To: <49223e65-a30b-7e0e-d545-35799d73b6f7@redhat.com>
On 08/31/2016 11:29 AM, Pedro Alves wrote:
> Please leave a breadcrumb comment here, like was done for
> target_read_memory, for example:
>
> /* For target_read_memory see target/target.h. */
>
Hit send too soon. Meant to say:
OK with that change.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-08-31 10:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 4:12 [PATCH 0/2] Consolidate target_{wait,resume} calls " Sergio Durigan Junior
2016-08-29 4:12 ` [PATCH 2/2] Share target_wait prototype " Sergio Durigan Junior
2016-08-31 10:29 ` Pedro Alves
2016-08-31 10:30 ` Pedro Alves [this message]
2016-09-01 18:58 ` Sergio Durigan Junior
2016-08-29 4:12 ` [PATCH 1/2] Use target_continue{,_no_signal} instead of target_resume Sergio Durigan Junior
2016-08-31 10:25 ` Pedro Alves
2016-09-01 18:57 ` 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=4942deb9-426d-856b-decf-22eb80744bb0@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).