From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: [PATCHv5-repost 1/2] qemu: make cirrus init value pci spec compliant
Date: Wed, 02 Dec 2009 15:43:28 +0200 [thread overview]
Message-ID: <4B166F00.1000505@redhat.com> (raw)
In-Reply-To: <20091202133306.GA18193@redhat.com>
On 12/02/2009 03:33 PM, Michael S. Tsirkin wrote:
> This for qemu.git
>
Please set the To: header correctly to avoid confusion.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-12-02 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1259607313.git.mst@redhat.com>
2009-11-30 19:02 ` [Qemu-devel] [PATCHv5-repost 1/2] qemu: make cirrus init value pci spec compliant Michael S. Tsirkin
2009-12-02 12:52 ` [Qemu-devel] " Avi Kivity
2009-12-02 13:33 ` Michael S. Tsirkin
2009-12-02 13:43 ` Avi Kivity [this message]
2009-11-30 19:02 ` [Qemu-devel] [PATCHv5-repost 2/2] qemu: cleanup unused macros in cirrus Michael S. Tsirkin
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=4B166F00.1000505@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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;
as well as URLs for NNTP newsgroup(s).