From: Amit Shah <amit.shah@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 16/19] qemu-char: move msmouse registeration to msmouse.c
Date: Tue, 5 Mar 2013 22:53:15 +0530 [thread overview]
Message-ID: <20130305172315.GA28191@amit.redhat.com> (raw)
In-Reply-To: <1361224096-21075-17-git-send-email-aliguori@us.ibm.com>
On (Mon) 18 Feb 2013 [15:48:13], Anthony Liguori wrote:
> +static CharDriverState *qemu_chr_open_pp(QemuOpts *opts)
> +{
> + return NULL;
> +}
I guess this was to fix up the compile broken by a previous commit.
I've handled this in my rebase.
Amit
next parent reply other threads:[~2013-03-05 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1361224096-21075-1-git-send-email-aliguori@us.ibm.com>
[not found] ` <1361224096-21075-17-git-send-email-aliguori@us.ibm.com>
2013-03-05 17:23 ` Amit Shah [this message]
2013-03-24 18:02 ` [Qemu-devel] [PATCH 00/19] chardev flow control Jan Kiszka
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=20130305172315.GA28191@amit.redhat.com \
--to=amit.shah@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@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).