From: David Hildenbrand <david@redhat.com>
To: Mark Kanda <mark.kanda@oracle.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, berrange@redhat.com
Subject: Re: [PATCH v2 0/2] Initialize backend memory objects in parallel
Date: Mon, 29 Jan 2024 14:41:02 +0100 [thread overview]
Message-ID: <7f42dae1-a859-4d78-afd3-916db5ed009f@redhat.com> (raw)
In-Reply-To: <57f6c99b-cdbc-4d4d-9988-e6e1fa307e4d@oracle.com>
On 29.01.24 14:39, Mark Kanda wrote:
> Ping.
>
> Any comments?
>
Sorry, fell through the cracks, will review this soonish.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-01-29 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 15:32 [PATCH v2 0/2] Initialize backend memory objects in parallel Mark Kanda
2024-01-22 15:32 ` [PATCH v2 1/2] oslib-posix: refactor memory prealloc threads Mark Kanda
2024-01-22 15:32 ` [PATCH v2 2/2] oslib-posix: initialize backend memory objects in parallel Mark Kanda
2024-01-29 13:39 ` [PATCH v2 0/2] Initialize " Mark Kanda
2024-01-29 13:41 ` David Hildenbrand [this message]
2024-01-29 19:11 ` David Hildenbrand
2024-01-29 22:59 ` Mark Kanda
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=7f42dae1-a859-4d78-afd3-916db5ed009f@redhat.com \
--to=david@redhat.com \
--cc=berrange@redhat.com \
--cc=mark.kanda@oracle.com \
--cc=pbonzini@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).