From: Eli Zaretskii <eliz@gnu.org>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 5/5] btrace: maintenance commands
Date: Wed, 24 Jun 2015 14:38:00 -0000 [thread overview]
Message-ID: <83616df9z9.fsf@gnu.org> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B2333166119@IRSMSX104.ger.corp.intel.com>
> From: "Metzger, Markus T" <markus.t.metzger@intel.com>
> CC: "palves@redhat.com" <palves@redhat.com>, "gdb-patches@sourceware.org"
> <gdb-patches@sourceware.org>
> Date: Wed, 24 Jun 2015 07:05:18 +0000
>
> > -----Original Message-----
> > From: Eli Zaretskii [mailto:eliz@gnu.org]
> > Sent: Tuesday, June 23, 2015 5:28 PM
> > To: Metzger, Markus T
> > Cc: palves@redhat.com; gdb-patches@sourceware.org
> > Subject: Re: [PATCH 5/5] btrace: maintenance commands
>
> Thanks for your quick review. Here are the parts I changed:
Thanks, this is good.
next prev parent reply other threads:[~2015-06-24 14:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 8:22 [PATCH 0/5] Support Intel(R) Processor Trace Markus Metzger
2015-06-23 8:22 ` [PATCH 4/5] btrace: store raw btrace data Markus Metzger
2015-06-30 12:56 ` Pedro Alves
2015-06-23 8:22 ` [PATCH 5/5] btrace: maintenance commands Markus Metzger
2015-06-23 15:28 ` Eli Zaretskii
2015-06-24 7:05 ` Metzger, Markus T
2015-06-24 14:38 ` Eli Zaretskii [this message]
2015-06-30 12:57 ` Pedro Alves
2015-06-23 8:22 ` [PATCH 1/5] configure: check for libipt Markus Metzger
2015-06-30 12:56 ` Pedro Alves
2015-06-30 14:54 ` Metzger, Markus T
2015-06-30 15:01 ` Pedro Alves
2015-06-23 8:22 ` [PATCH 3/5] btrace, linux: use data_size and data_offset Markus Metzger
2015-06-30 12:56 ` Pedro Alves
2015-06-23 8:23 ` [PATCH 2/5] btrace: support Intel(R) Processor Trace Markus Metzger
2015-06-23 15:32 ` Eli Zaretskii
2015-06-30 12:56 ` Pedro Alves
2015-06-30 14:54 ` Metzger, Markus T
2015-06-30 15:08 ` Pedro Alves
2015-07-01 8:39 ` Metzger, Markus T
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=83616df9z9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--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