From: Yao Qi <qiyaoltc@gmail.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Assert on lval_register
Date: Tue, 06 Dec 2016 14:26:00 -0000 [thread overview]
Message-ID: <20161206142635.GB28789@E107787-LIN> (raw)
In-Reply-To: <20161206131328.D7D4810FC4B@oc8523832656.ibm.com>
On 16-12-06 14:13:28, Ulrich Weigand wrote:
>
> > OK, how about the patch below?
>
> Looks good to me.
>
Patch is pushed in.
--
Yao (é½å°§)
prev parent reply other threads:[~2016-12-06 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 14:56 Yao Qi
2016-11-30 21:16 ` Ulrich Weigand
2016-12-06 10:15 ` Yao Qi
2016-12-06 13:13 ` Ulrich Weigand
2016-12-06 14:26 ` Yao Qi [this message]
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=20161206142635.GB28789@E107787-LIN \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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