From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Pedro Alves <palves@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"jan.kratochvil@redhat.com" <jan.kratochvil@redhat.com>,
"tromey@redhat.com" <tromey@redhat.com>,
"kettenis@gnu.org" <kettenis@gnu.org>
Subject: RE: [patch v5 07/12] btrace, doc: document remote serial protocol
Date: Fri, 14 Dec 2012 07:53:00 -0000 [thread overview]
Message-ID: <A78C989F6D9628469189715575E55B2307B3F769@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <50CA0BA6.5070507@redhat.com>
> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Thursday, December 13, 2012 6:09 PM
> To: Metzger, Markus T
> Cc: Eli Zaretskii; gdb-patches@sourceware.org; jan.kratochvil@redhat.com; palves@redhat.com; tromey@redhat.com;
> kettenis@gnu.org
> Subject: Re: [patch v5 07/12] btrace, doc: document remote serial protocol
>
> On 12/13/2012 08:43 AM, Metzger, Markus T wrote:
>
> > I will keep the patch in the series until the entire series has been approved. Do you want me to omit this patch when sending out
> updates of the series?
>
> Please keep it in the series. The mechanics of the docs might be
> approved, but someone should still go over the packet's semantics,
> and its just to easier on someone looking at the whole thing
> if things are kept together, instead of having the reader hunt
> for bits and pieces.
OK, I'll keep sending this patch and add a note to the cover letter that rsp doc has been approved.
Are you OK with the changes I made in response to your feedback, Pedro? I will also address the explicit == NULL and != NULL checks in the next update. Is there anything else that needs changing?
Regards,
Markus.
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
next prev parent reply other threads:[~2012-12-14 7:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 10:37 [patch v5 00/12] branch tracing support for Atom markus.t.metzger
2012-12-07 10:37 ` [patch v5 09/12] gdbserver, linux, btrace: add btrace support for linux-low markus.t.metzger
2012-12-07 10:37 ` [patch v5 06/12] remote, btrace: add branch trace remote ops markus.t.metzger
2012-12-07 10:38 ` [patch v5 03/12] linux, btrace: perf_event based branch tracing markus.t.metzger
2012-12-07 10:38 ` [patch v5 02/12] cli, btrace: add btrace cli markus.t.metzger
2012-12-07 15:16 ` Eli Zaretskii
2012-12-13 9:14 ` Metzger, Markus T
2012-12-07 10:38 ` [patch v5 01/12] thread, btrace: add generic branch trace support markus.t.metzger
2012-12-07 10:38 ` [patch v5 10/12] test, btrace: add branch tracing tests markus.t.metzger
2012-12-07 10:38 ` [patch v5 08/12] gdbserver, btrace: add generic btrace support markus.t.metzger
2012-12-07 10:38 ` [patch v5 07/12] btrace, doc: document remote serial protocol markus.t.metzger
2012-12-07 15:09 ` Eli Zaretskii
2012-12-13 8:43 ` Metzger, Markus T
2012-12-13 17:02 ` Eli Zaretskii
2012-12-13 17:09 ` Pedro Alves
2012-12-14 7:53 ` Metzger, Markus T [this message]
2012-12-07 10:38 ` [patch v5 04/12] linux, i386, amd64: enable btrace for 32bit and 64bit linux native markus.t.metzger
2012-12-07 10:38 ` [patch v5 12/12] btrace, x86: disable on some processors markus.t.metzger
2012-12-07 10:38 ` [patch v5 05/12] xml, btrace: define btrace xml document style markus.t.metzger
2012-12-07 10:39 ` [patch v5 11/12] test, btrace: more branch tracing tests markus.t.metzger
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=A78C989F6D9628469189715575E55B2307B3F769@IRSMSX102.ger.corp.intel.com \
--to=markus.t.metzger@intel.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=kettenis@gnu.org \
--cc=palves@redhat.com \
--cc=tromey@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