From: Paolo Bonzini <pbonzini@redhat.com>
To: Matt Borgerson <contact@mborgerson.com>, Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, rth@twiddle.net
Subject: Re: [PATCH] memory: Fix start offset for bitmap log_clear hook
Date: Mon, 2 Mar 2020 17:34:35 +0100 [thread overview]
Message-ID: <dea85039-5bf2-8de6-471a-8e4bd56f1166@redhat.com> (raw)
In-Reply-To: <CADc=-s4nkB6ieakmiRuogygT7dzjb3q--noAWEALrrSOG+ZN2w@mail.gmail.com>
On 25/02/20 21:46, Matt Borgerson wrote:
> [ ping ]
>
> Hi Paolo, would you mind taking a quick look at this patch for
> memory.c to consider
> it for merge? This resolves an issue with dirty bits not being cleared
> as expected.
>
> Here's the Patchwork link: http://patchwork.ozlabs.org/patch/1240121/
>
> Thanks for your time!
Yes, I queued it now.
Thanks!
Paolo
prev parent reply other threads:[~2020-03-02 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 10:19 [PATCH] memory: Fix start offset for bitmap log_clear hook Matt Borgerson
2020-02-18 16:53 ` Peter Xu
2020-02-25 20:46 ` Matt Borgerson
2020-03-02 16:34 ` Paolo Bonzini [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=dea85039-5bf2-8de6-471a-8e4bd56f1166@redhat.com \
--to=pbonzini@redhat.com \
--cc=contact@mborgerson.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).