public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: <gdb-patches@sourceware.org>,  Par Olsson <par.olsson@windriver.com>
Subject: Re: [PATCH 1/2] Fix write endianness/size problem for fast tracepoint enabled flag
Date: Thu, 05 May 2016 07:58:00 -0000	[thread overview]
Message-ID: <86inytc4xk.fsf@gmail.com> (raw)
In-Reply-To: <1459351018-23718-1-git-send-email-simon.marchi@ericsson.com>	(Simon Marchi's message of "Wed, 30 Mar 2016 11:16:57 -0400")

Simon Marchi <simon.marchi@ericsson.com> writes:

Hi Simon,

> gdb/gdbserver/ChangeLog:
>
> YYYY-MM-DD  Par Olsson  <par.olsson@windriver.com>
>
> 	* tracepoint.c (write_inferior_int8): New function.
> 	(cmd_qtenable_disable): Write enable flag using
> 	write_inferior_int8.

The format of committed changelog entry looks odd to me,

2016-04-28  Par Olsson  <par.olsson@windriver.com>
2016-04-28  Simon Marchi  <simon.marchi@ericsson.com>

	* tracepoint.c (write_inferior_int8): New function.
	(cmd_qtenable_disable): Write enable flag using
	write_inferior_int8.

-- 
Yao (齐尧)

  parent reply	other threads:[~2016-05-05  7:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 15:17 Simon Marchi
2016-03-30 15:17 ` [PATCH 2/2] Add test for fast tracepoint enable/disable Simon Marchi
2016-03-31 10:58   ` Yao Qi
2016-03-31 18:01     ` Simon Marchi
2016-03-31 18:31       ` Simon Marchi
2016-04-01 13:36       ` Yao Qi
2016-04-01 14:42         ` Simon Marchi
2016-04-28 15:30     ` Simon Marchi
2016-04-28 16:03       ` Yao Qi
2016-04-28 16:57         ` Simon Marchi
2016-03-31 10:51 ` [PATCH 1/2] Fix write endianness/size problem for fast tracepoint enabled flag Yao Qi
2016-03-31 11:33   ` Pedro Alves
2016-03-31 12:58     ` Yao Qi
2016-03-31 17:45   ` Simon Marchi
2016-05-05  7:58 ` Yao Qi [this message]
2016-05-05 13:50   ` Simon Marchi

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=86inytc4xk.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=par.olsson@windriver.com \
    --cc=simon.marchi@ericsson.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).