From: Yao Qi <qiyaoltc@gmail.com>
To: Alan Hayward <Alan.Hayward@arm.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:43:00 -0000 [thread overview]
Message-ID: <86r30ep4ml.fsf@gmail.com> (raw)
In-Reply-To: <B40E247A-422D-426A-8E17-74811D0DFFD7@arm.com> (Alan Hayward's message of "Wed, 26 Apr 2017 14:03:13 +0000")
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.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-04-27 9:43 UTC|newest]
Thread overview: 17+ 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
2017-04-05 16:01 ` Yao Qi
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 [this message]
2017-04-27 9:52 ` Alan Hayward
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=86r30ep4ml.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.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).