qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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] [PULL][v2] Memory API fix
Date: Mon, 22 Aug 2011 19:54:08 +0300	[thread overview]
Message-ID: <4E5289B0.9060705@redhat.com> (raw)

[v2: fix git url...]

Anthony, please pull from:

   git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/core

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.


(and I'll take this opportunity to announce a new layout for the branch:

  - memory/core - core fixes, usually not rebased
  - memory/batch - pending batch
  - memory/queue - the rest of the patches in my queue
  - memory/master - a merge of the first three; please post patches 
based on this branch

this will allow me to fast-path core fixes without rebasing 
memory/batch, except when a dependency is involved.)

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

             reply	other threads:[~2011-08-22 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 16:54 Avi Kivity [this message]
2011-08-22 17:16 ` [Qemu-devel] Merging invasive changes (Was Re: [PULL][v2] Memory API fix) Anthony Liguori
2011-08-22 17:29 ` [Qemu-devel] [PULL][v2] Memory API fix 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=4E5289B0.9060705@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 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).