From: "Michal Prívozník" <mprivozn@redhat.com>
To: David Hildenbrand <david@redhat.com>, qemu-devel@nongnu.org
Cc: imammedo@redhat.com, marcandre.lureau@redhat.com, berrange@redhat.com
Subject: Re: [PATCH v2] hostmem: Honor multiple preferred nodes if possible
Date: Mon, 19 Dec 2022 12:10:32 +0100 [thread overview]
Message-ID: <88d57d47-09e5-ebd8-82aa-f289a05e0517@redhat.com> (raw)
In-Reply-To: <302262b2-e928-7013-3f4e-4ab5a9616844@redhat.com>
On 12/19/22 10:58, David Hildenbrand wrote:
>
> I'll fixup. I just queued the fixed-up patch to
>
> https://github.com/davidhildenbrand/qemu.git mem-next
>
> Please double-check. Thanks!
>
Looks good. Sorry for not doing it properly the first time.
Michal
next prev parent reply other threads:[~2022-12-19 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 9:55 [PATCH v2] hostmem: Honor multiple preferred nodes if possible Michal Privoznik
2022-12-16 13:41 ` David Hildenbrand
2022-12-16 13:47 ` Michal Prívozník
2022-12-19 9:55 ` David Hildenbrand
2022-12-19 9:57 ` Michal Prívozník
2022-12-19 9:58 ` David Hildenbrand
2022-12-19 11:10 ` Michal Prívozník [this message]
2022-12-19 15:23 ` David Hildenbrand
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=88d57d47-09e5-ebd8-82aa-f289a05e0517@redhat.com \
--to=mprivozn@redhat.com \
--cc=berrange@redhat.com \
--cc=david@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcandre.lureau@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).