From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel <qemu-devel@nongnu.org>
Cc: KVM list <kvm@vger.kernel.org>
Subject: [GIT PULL] Memory API fixes
Date: Mon, 22 Aug 2011 18:42:13 +0300 [thread overview]
Message-ID: <4E5278D5.6040104@redhat.com> (raw)
Anthony, please pull from:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
refs/tags/memory-region-fixes-1
to receive a memory API fix. The fix is not required for any of the
already merged patches, but is needed by other patches in my queue.
I am sending core patches separately than the conversions to increase
their visibility.
Richard Henderson (1):
memory: Fix old_portio vs non-zero offset
memory.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel <qemu-devel@nongnu.org>
Cc: KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] [GIT PULL] Memory API fixes
Date: Mon, 22 Aug 2011 18:42:13 +0300 [thread overview]
Message-ID: <4E5278D5.6040104@redhat.com> (raw)
Anthony, please pull from:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
refs/tags/memory-region-fixes-1
to receive a memory API fix. The fix is not required for any of the
already merged patches, but is needed by other patches in my queue.
I am sending core patches separately than the conversions to increase
their visibility.
Richard Henderson (1):
memory: Fix old_portio vs non-zero offset
memory.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2011-08-22 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 15:42 Avi Kivity [this message]
2011-08-22 15:42 ` [Qemu-devel] [GIT PULL] Memory API fixes Avi Kivity
2011-08-22 16:24 ` Anthony Liguori
2011-08-22 16:24 ` Anthony Liguori
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=4E5278D5.6040104@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--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.