From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PULL][v2] Memory API fix
Date: Mon, 22 Aug 2011 12:29:12 -0500 [thread overview]
Message-ID: <4E5291E8.3060106@codemonkey.ws> (raw)
In-Reply-To: <4E5289B0.9060705@redhat.com>
On 08/22/2011 11:54 AM, Avi Kivity wrote:
> [v2: fix git url...]
>
> Anthony, please pull from:
>
> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/core
Pulled. Thanks.
Regards,
Anthony Liguori
>
> 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(-)
>
prev parent reply other threads:[~2011-08-22 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 16:54 [PULL][v2] Memory API fix Avi Kivity
2011-08-22 16:54 ` [Qemu-devel] " Avi Kivity
2011-08-22 17:16 ` Merging invasive changes (Was Re: [Qemu-devel] [PULL][v2] Memory API fix) Anthony Liguori
2011-08-22 17:16 ` [Qemu-devel] Merging invasive changes (Was " Anthony Liguori
2011-08-22 17:29 ` Anthony Liguori [this message]
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=4E5291E8.3060106@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=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.