From: Yao Qi <yao@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [ping 2]: [PATCH v4 0/5] MI notification on trace started/stopped
Date: Tue, 04 Jun 2013 09:20:00 -0000 [thread overview]
Message-ID: <51ADB16E.3070008@codesourcery.com> (raw)
In-Reply-To: <516F3C05.2030603@redhat.com>
On 04/18/2013 08:19 AM, Pedro Alves wrote:
> Next up, as I said before, is the range stepping
> series. Please let me focus on it and get it to completion, and context
> switch to the async notifications afterwards.
Hi, Pedro,
Could you review the async notification patch series recently? The V4
still applies to FSF GDB trunk (as of May 30th) and regression test on
x86_64-linux shows no regression.
--
Yao (é½å°§)
prev parent reply other threads:[~2013-06-04 9:20 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 7:05 [PATCH 0/5] MI notification on trace started/stopped (V3) Yao Qi
2013-01-22 7:05 ` [PATCH 2/5] Query supported notifications by qSupported Yao Qi
2013-01-22 8:09 ` Eli Zaretskii
2013-01-22 8:41 ` Yao Qi
2013-01-22 10:26 ` Eli Zaretskii
2013-01-22 7:05 ` [PATCH 3/5] async remote notification 'Trace' Yao Qi
2013-01-22 8:06 ` Eli Zaretskii
2013-01-22 7:05 ` [PATCH 1/5] Add annex in a async remote notification Yao Qi
2013-01-22 8:06 ` Eli Zaretskii
2013-02-16 3:40 ` Yao Qi
2013-02-16 9:27 ` Eli Zaretskii
2013-03-29 17:17 ` Yao Qi
2013-03-31 0:39 ` Eli Zaretskii
2013-01-22 7:06 ` [PATCH 4/5] MI notification on trace started/stopped:basic Yao Qi
2013-01-22 8:11 ` Eli Zaretskii
2013-01-22 7:06 ` [PATCH 5/5] MI notification on trace stop: triggered by remote Yao Qi
2013-01-30 4:00 ` [ping]: [PATCH 0/5] MI notification on trace started/stopped (V3) Yao Qi
2013-02-07 12:41 ` [ping 2]: " Yao Qi
2013-02-16 4:01 ` [PATCH 0/5] MI notification on trace started/stopped (V3.1) Yao Qi
2013-02-16 4:01 ` [PATCH 1/5] Add annex in a async remote notification Yao Qi
2013-02-16 9:27 ` Eli Zaretskii
2013-02-16 4:02 ` [PATCH 3/5] async remote notification 'Trace' Yao Qi
2013-02-16 9:34 ` Eli Zaretskii
2013-02-16 4:02 ` [PATCH 2/5] Query supported notifications by qSupported Yao Qi
2013-02-16 9:33 ` Eli Zaretskii
2013-03-11 9:26 ` Yao Qi
2013-03-11 16:59 ` Eli Zaretskii
2013-02-16 4:02 ` [PATCH 5/5] MI notification on trace stop: triggered by remote Yao Qi
2013-02-16 4:02 ` [PATCH 4/5] MI notification on trace started/stopped:basic Yao Qi
2013-02-16 9:36 ` Eli Zaretskii
2013-02-25 3:14 ` ping: [PATCH 0/5] MI notification on trace started/stopped (V3.1) Yao Qi
2013-03-04 2:34 ` ping^2 : " Yao Qi
2013-04-02 2:33 ` [PATCH v4 0/5] MI notification on trace started/stopped Yao Qi
2013-04-02 3:15 ` [PATCH 2/5] Query supported notifications by qSupported Yao Qi
2013-04-02 3:58 ` [PATCH 3/5] async remote notification 'Trace' Yao Qi
2013-04-02 12:46 ` [PATCH 5/5] MI notification on trace stop: triggered by remote Yao Qi
2013-04-02 13:07 ` [PATCH 4/5] MI notification on trace started/stopped:basic Yao Qi
2013-04-02 13:30 ` [PATCH 1/5] Add annex in a async remote notification Yao Qi
2013-04-10 15:46 ` [PATCH v4 0/5] MI notification on trace started/stopped Yao Qi
2013-04-17 14:37 ` [ping 2]: " Yao Qi
2013-04-18 15:16 ` Pedro Alves
2013-04-18 16:14 ` Yao Qi
2013-06-04 9:20 ` 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=51ADB16E.3070008@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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