From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] Simplify cpu_register_io_memory() a bit
Date: Sun, 31 May 2009 17:11:35 +0300 [thread overview]
Message-ID: <4A229017.5060207@redhat.com> (raw)
In-Reply-To: <1243776797-23772-1-git-send-email-avi@redhat.com>
Missed the blurb:
This small patchset removes the unused io_index parameter from
cpu_register_io_memory(), making future simplification of this
mechanism a tiny bit simpler.
The diffstat looks frightening, but the changes are quite simple
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH 0/2] Simplify cpu_register_io_memory() a bit
Date: Sun, 31 May 2009 17:11:35 +0300 [thread overview]
Message-ID: <4A229017.5060207@redhat.com> (raw)
In-Reply-To: <1243776797-23772-1-git-send-email-avi@redhat.com>
Missed the blurb:
This small patchset removes the unused io_index parameter from
cpu_register_io_memory(), making future simplification of this
mechanism a tiny bit simpler.
The diffstat looks frightening, but the changes are quite simple
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-31 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-31 13:33 [PATCH 0/2] Simplify cpu_register_io_memory() a bit Avi Kivity
2009-05-31 13:33 ` [Qemu-devel] " Avi Kivity
2009-05-31 13:33 ` [PATCH 1/2] Remove io_index argument from cpu_register_io_memory() Avi Kivity
2009-05-31 13:33 ` [Qemu-devel] " Avi Kivity
2009-05-31 13:33 ` [PATCH 2/2] Rearrange io_mem_init() Avi Kivity
2009-05-31 13:33 ` [Qemu-devel] " Avi Kivity
2009-05-31 14:11 ` Avi Kivity [this message]
2009-05-31 14:11 ` [Qemu-devel] Re: [PATCH 0/2] Simplify cpu_register_io_memory() a bit Avi Kivity
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=4A229017.5060207@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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.