From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] Factor remote_read_bytes.
Date: Fri, 21 Mar 2014 11:57:00 -0000 [thread overview]
Message-ID: <532C290D.8000808@redhat.com> (raw)
In-Reply-To: <1394541731-27486-2-git-send-email-yao@codesourcery.com>
On 03/11/2014 12:42 PM, Yao Qi wrote:
> This patch moves code in remote_read_bytes on reading from the remote
> stub to a new function remote_read_bytes_1.
>
> gdb:
>
> 2014-03-11 Yao Qi <yao@codesourcery.com>
>
> * remote.c (remote_read_bytes): Move code on reading from the
> remote stub to ...
> (remote_read_bytes_1): ... here. New function.
OK.
Thanks,
--
Pedro Alves
next prev parent reply other threads:[~2014-03-21 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 12:44 [PATCH 1/3] Move the traceframe_available_memory code from memory_xfer_partial_1 down to the targets Yao Qi
2014-03-11 12:45 ` [PATCH 3/3] Remove target_read_live_memory Yao Qi
2014-03-21 12:01 ` Pedro Alves
2014-03-22 11:23 ` Yao Qi
2014-03-11 12:45 ` [PATCH 2/3] Factor remote_read_bytes Yao Qi
2014-03-21 11:57 ` Pedro Alves [this message]
2014-03-21 9:41 ` [PATCH 1/3] Move the traceframe_available_memory code from memory_xfer_partial_1 down to the targets Yao Qi
2014-03-21 11:56 ` Pedro Alves
2014-03-22 11:20 ` Yao Qi
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=532C290D.8000808@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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