From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 0/3] qxl trace events
Date: Mon, 19 Mar 2012 12:58:31 +0100 [thread overview]
Message-ID: <4F671F67.8000800@redhat.com> (raw)
In-Reply-To: <1332074775-31270-1-git-send-email-alevy@redhat.com>
On 03/18/12 13:46, Alon Levy wrote:
> Alon Levy (3):
> qxl: init_pipe_signaling: exit on failure
> qxl: switch qxl.c to trace-events
> qxl/qxl_render.c: add trace events
Patch added to spice patch queue.
thanks,
Gerd
prev parent reply other threads:[~2012-03-19 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 12:46 [Qemu-devel] [PATCH v4 0/3] qxl trace events Alon Levy
2012-03-18 12:46 ` [Qemu-devel] [PATCH v4 1/3] qxl: init_pipe_signaling: exit on failure Alon Levy
2012-03-18 12:46 ` [Qemu-devel] [PATCH v4 2/3] qxl: switch qxl.c to trace-events Alon Levy
2012-03-18 12:46 ` [Qemu-devel] [PATCH v4 3/3] qxl/qxl_render.c: add trace events Alon Levy
2012-03-19 11:58 ` Gerd Hoffmann [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=4F671F67.8000800@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).