From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix gdb.trace/ ftrace tests
Date: Wed, 06 Dec 2017 15:58:00 -0000 [thread overview]
Message-ID: <86fu8nq25r.fsf@gmail.com> (raw)
In-Reply-To: <1512573424-26651-1-git-send-email-palves@redhat.com> (Pedro Alves's message of "Wed, 6 Dec 2017 15:17:04 +0000")
Pedro Alves <palves@redhat.com> writes:
> gdb/testsuite/ChangeLog:
> 2017-12-06 Pedro Alves <palves@redhat.com>
>
> * gdb.trace/ftrace-lock.exp: Pass "-q" to break/ftrace.
> * gdb.trace/ftrace.exp (test_fast_tracepoints): Likewise.
> * gdb.trace/trace-break.exp (break_trace_same_addr_1)
> (break_trace_same_addr_2, break_trace_same_addr_3)
> (break_trace_same_addr_4, break_trace_same_addr_5)
> (break_trace_same_addr_6): Pass "-q" to break/trace/ftrace.
> * gdb.trace/trace-condition.exp (test_tracepoints): Likewise.
> * gdb.trace/trace-mt.exp (break_trace_same_addr): Likewise.
Patch is good to me.
--
Yao (齐尧)
prev parent reply other threads:[~2017-12-06 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 15:17 Pedro Alves
2017-12-06 15:58 ` 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=86fu8nq25r.fsf@gmail.com \
--to=qiyaoltc@gmail.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