From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] ioapic: Convert to memory API
Date: Mon, 17 Oct 2011 16:57:02 +0200 [thread overview]
Message-ID: <4E9C423E.5020808@redhat.com> (raw)
In-Reply-To: <4E9C0D5F.404@siemens.com>
On 10/17/2011 01:11 PM, Jan Kiszka wrote:
> This maintains the old imprecise access size handling.
>
Thanks, applied both to memory/queue.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-10-17 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 17:21 [Qemu-devel] [PATCH] ioapic: Convert to memory API Jan Kiszka
2011-10-17 10:35 ` Avi Kivity
2011-10-17 11:11 ` [Qemu-devel] [PATCH v2 1/2] " Jan Kiszka
2011-10-17 14:57 ` Avi Kivity [this message]
2011-10-17 11:11 ` [Qemu-devel] [PATCH 2/2] ioapic: Reject non-dword accesses to IOWIN register 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=4E9C423E.5020808@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.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 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.