From: Alan Hayward <Alan.Hayward@arm.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH] Remove MAX_REGISTER_SIZE from regcache.c
Date: Thu, 27 Apr 2017 09:52:00 -0000 [thread overview]
Message-ID: <3418367D-9E13-49C7-9C9B-91B0DC1AB0A4@arm.com> (raw)
In-Reply-To: <86r30ep4ml.fsf@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 921 bytes --]
> On 27 Apr 2017, at 10:43, Yao Qi <qiyaoltc@gmail.com> wrote:
>
> Alan Hayward <Alan.Hayward@arm.com> writes:
>
>> Ok to commit?
>>
>> Alan.
>>
>> 2017-04-26 Alan Hayward <alan.hayward@arm.com>
>>
>> * regcache.c (regcache_save): Avoid buffer use.
>> (regcache_dump): Avoid buffer use.
>
> Hi Alan,
> Patch is good to me, but it has conflict with my patches
>
> [PATCH 0/6] Class-fy regcache in GDB
> https://sourceware.org/ml/gdb-patches/2017-04/msg00684.html
>
> Can you postpone pushing this patch until my patches are committed? You
> then need to rebase your patch. I've rebased my patch sets twice before
> I posted them. Considering the size of your patch, it takes less
> effort to rebase yours.
>
Thatâs fine. My rebase should be easy enough.
If you remember, could you let me know when you have pushed your patch.
Alan.
\x16º&Öéj×!zÊÞ¶êç×\x7f:ã¹b²Ö«r\x18\x1dnr\x17¬
next prev parent reply other threads:[~2017-04-27 9:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 10:19 Alan Hayward
2017-03-23 14:45 ` Alan Hayward
2017-03-24 8:49 ` Yao Qi
2017-03-24 10:28 ` Alan Hayward
2017-04-05 14:53 ` Alan Hayward
[not found] ` <868tneq1xj.fsf@gmail.com>
2017-04-05 18:10 ` Alan Hayward
2017-04-10 8:59 ` Yao Qi
2017-04-10 10:53 ` Alan Hayward
2017-04-21 14:01 ` Yao Qi
2017-04-26 14:03 ` Alan Hayward
2017-04-27 9:43 ` Yao Qi
2017-04-27 9:52 ` Alan Hayward [this message]
2017-05-03 8:21 ` Yao Qi
2017-05-03 10:42 ` Alan Hayward
2017-06-07 8:49 ` Alan Hayward
2017-06-07 9:12 ` 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=3418367D-9E13-49C7-9C9B-91B0DC1AB0A4@arm.com \
--to=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=qiyaoltc@gmail.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