From: Juan Quintela <quintela@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Split ram_save_block
Date: Mon, 12 May 2014 12:36:42 +0200 [thread overview]
Message-ID: <87d2fj8erp.fsf@elfo.mitica> (raw)
In-Reply-To: <1399632895-17675-1-git-send-email-dgilbert@redhat.com> (David Alan Gilbert's message of "Fri, 9 May 2014 11:54:55 +0100")
"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com> wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> ram_save_block is getting a bit too complicated, and does two separate
> things:
> 1) Finds a page to send
> 2) Sends the page (dealing with compression etc)
>
> Split into 'ram_save_page' to send the page and deal with compression (2)
> Rename remaining function to 'ram_find_and_save_block'
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
prev parent reply other threads:[~2014-05-12 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 10:54 [Qemu-devel] [PATCH] Split ram_save_block Dr. David Alan Gilbert (git)
2014-05-12 10:36 ` Juan Quintela [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=87d2fj8erp.fsf@elfo.mitica \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.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 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).