qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] Makefile.target: code stp dependency on trace-events
Date: Mon, 19 Mar 2012 12:28:17 +0000	[thread overview]
Message-ID: <20120319122817.GA32105@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <1332056835-21143-1-git-send-email-alevy@redhat.com>

On Sun, Mar 18, 2012 at 08:47:15AM +0100, Alon Levy wrote:
> Signed-off-by: Alon Levy <alevy@redhat.com>
> ---
>  Makefile.target |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Nice catch, thanks!

Applied to the tracing patches tree:
https://github.com/stefanha/qemu/commits/tracing

Stefan

      reply	other threads:[~2012-03-19 12:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-18  7:47 [Qemu-devel] [PATCH] Makefile.target: code stp dependency on trace-events Alon Levy
2012-03-19 12:28 ` Stefan Hajnoczi [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=20120319122817.GA32105@stefanha-thinkpad.localdomain \
    --to=stefanha@gmail.com \
    --cc=alevy@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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 NNTP newsgroup(s).