All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCHv3 0/3] trace: improve hypercall tracing
Date: Thu, 31 May 2012 15:32:17 +0100	[thread overview]
Message-ID: <4FC780F1.201@citrix.com> (raw)
In-Reply-To: <CAFLBxZZ6uRj3vwSv4k1=ejCyftcDP-G6WAM4CTYynyhhHDn0YA@mail.gmail.com>

On 31/05/12 15:21, George Dunlap wrote:
> On Thu, May 31, 2012 at 12:06 PM, David Vrabel <david.vrabel@citrix.com> wrote:
>> These are probably for 4.3.
> 
> Thanks for doing these, David.

Thanks for the review.

> I wouldn't oppose these going into 4.2;  but it is getting awfully
> late.  (I acked them "4.2-only" just to flag that up to the
> committers.)

I think they should be for 4.3 -- there's more important things needing
to be merged into 4.2.

> BTW, what did you use to send these patches?  Any chance you could use
> "hg email" (or the git equivalent if you're using git) instead?  It
> makes it a lot easier for me to integrate them into my review
> workflow. :-)

I did use git send-email.  What's the problem with the series? I can see
if there options I could turn on that would help.

David

  reply	other threads:[~2012-05-31 14:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 11:06 [PATCHv3 0/3] trace: improve hypercall tracing David Vrabel
2012-05-31 11:06 ` [PATCH 1/3] trace: allow for different sub-classes of TRC_PV_* tracepoints David Vrabel
2012-05-31 14:13   ` George Dunlap
2012-05-31 11:06 ` [PATCH 2/3] trace: improve usefulness of hypercall trace record David Vrabel
2012-05-31 14:14   ` George Dunlap
2012-05-31 11:06 ` [PATCH 3/3] trace: trace hypercalls inside a multicall David Vrabel
2012-05-31 14:15   ` George Dunlap
2012-05-31 14:21 ` [PATCHv3 0/3] trace: improve hypercall tracing George Dunlap
2012-05-31 14:32   ` David Vrabel [this message]
2012-06-01 16:17     ` George Dunlap

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=4FC780F1.201@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.