From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Nikolai Barybin" <nikolai.barybin@virtuozzo.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel@nongnu.org, "Denis V . Lunev" <den@virtuozzo.com>,
Ani Sinha <anisinha@redhat.com>
Subject: Re: [PATCH v4 0/2] dump: enhance win_dump_available to report properly
Date: Tue, 23 Sep 2025 17:33:31 +0100 [thread overview]
Message-ID: <aNLL24Fjt8XAwLgf@redhat.com> (raw)
In-Reply-To: <20250911123656.413160-1-nikolai.barybin@virtuozzo.com>
Marc-André, are these patches good with you ? From my POV they're
ready to be queued.
On Thu, Sep 11, 2025 at 03:36:54PM +0300, Nikolai Barybin wrote:
> Changes since last revision:
> - Split in 2 patches
>
> Nikolai Barybin (2):
> dump: enhance dump_state_prepare fd initialization
> dump: enhance win_dump_available to report properly
>
> dump/dump.c | 138 ++++++++++++++++++++++++++++--------------------
> dump/win_dump.c | 23 ++++++--
> dump/win_dump.h | 2 +-
> 3 files changed, 101 insertions(+), 62 deletions(-)
>
> --
> 2.43.5
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2025-09-23 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 12:36 [PATCH v4 0/2] dump: enhance win_dump_available to report properly Nikolai Barybin
2025-09-11 12:36 ` [PATCH v4 1/2] dump: enhance dump_state_prepare fd initialization Nikolai Barybin
2025-09-11 12:36 ` [PATCH v4 2/2] dump: enhance win_dump_available to report properly Nikolai Barybin
2025-09-24 8:27 ` Marc-André Lureau
2026-01-08 8:11 ` Marc-André Lureau
2026-01-08 9:30 ` Denis V. Lunev
2026-06-05 16:10 ` Daniel P. Berrangé
2026-06-05 16:20 ` Denis V. Lunev
2025-09-23 16:33 ` Daniel P. Berrangé [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=aNLL24Fjt8XAwLgf@redhat.com \
--to=berrange@redhat.com \
--cc=anisinha@redhat.com \
--cc=den@virtuozzo.com \
--cc=marcandre.lureau@redhat.com \
--cc=nikolai.barybin@virtuozzo.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 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.