From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: "Huang, FangSheng (Jerry)" <FangSheng.Huang@amd.com>,
qemu-devel@nongnu.org, imammedo@redhat.com
Cc: Zhigang.Luo@amd.com, Lianjie.Shi@amd.com,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v2] numa: add 'spm' option for Specific Purpose Memory
Date: Mon, 3 Nov 2025 13:36:49 +0100 [thread overview]
Message-ID: <07c41b89-2e4b-423c-9577-93001112b04d@kernel.org> (raw)
In-Reply-To: <1fc33dfc-ae73-4d23-a21a-a3a5ed480dd1@amd.com>
On 03.11.25 04:01, Huang, FangSheng (Jerry) wrote:
> Hi David,
Hi!
>
> I hope this email finds you well. I wanted to follow up on the SPM
> patch series we discussed back in October.
>
> I'm reaching out to check on the current status and see if there's
> anything else I should address or any additional information I can
> provide.
>
> Thank you for your time and guidance on this!
I just commented on the implementation, I think it can be simplified.
Regarding the overall idea it would be great to learn whether Igor as
any more concerns.
Cheers,
David
prev parent reply other threads:[~2025-11-03 14:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 9:07 [PATCH v2] numa: add 'spm' option for Specific Purpose Memory fanhuang
2025-10-20 9:07 ` fanhuang
2025-11-03 12:32 ` David Hildenbrand
2025-11-04 8:00 ` Huang, FangSheng (Jerry)
2025-12-08 10:51 ` [PATCH v3 0/1] " fanhuang
2025-12-08 10:51 ` [PATCH v3 1/1] " fanhuang
2025-12-08 16:57 ` Jonathan Cameron via
2025-10-20 10:15 ` [PATCH v2] " Jonathan Cameron via
2025-10-20 20:03 ` David Hildenbrand
2025-10-22 10:19 ` Huang, FangSheng (Jerry)
2025-10-20 20:10 ` David Hildenbrand
2025-10-22 10:09 ` Huang, FangSheng (Jerry)
2025-10-22 10:28 ` David Hildenbrand
2025-11-03 3:01 ` Huang, FangSheng (Jerry)
2025-11-03 12:36 ` David Hildenbrand (Red Hat) [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=07c41b89-2e4b-423c-9577-93001112b04d@kernel.org \
--to=david@kernel.org \
--cc=FangSheng.Huang@amd.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Lianjie.Shi@amd.com \
--cc=Zhigang.Luo@amd.com \
--cc=imammedo@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).