[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eb3e6ae9-d296-465f-a5a9-963da4d8ce6a@kernel.org>
Date: Thu, 15 Jan 2026 18:26:21 +0100
From: "David Hildenbrand (Red Hat)" <david@...nel.org>
To: Gregory Price <gourry@...rry.net>, linux-mm@...ck.org
Cc: linux-cxl@...r.kernel.org, nvdimm@...ts.linux.dev,
linux-kernel@...r.kernel.org, virtualization@...ts.linux.dev,
kernel-team@...a.com, dan.j.williams@...el.com, vishal.l.verma@...el.com,
dave.jiang@...el.com, mst@...hat.com, jasowang@...hat.com,
xuanzhuo@...ux.alibaba.com, eperezma@...hat.com, osalvador@...e.de,
akpm@...ux-foundation.org
Subject: Re: [PATCH v2 0/5] add runtime hotplug state control
On 1/15/26 00:50, Gregory Price wrote:
> The dax kmem driver currently onlines memory automatically during
> probe using the system's default online policy but provides no way
> to control or query the entire region state at runtime.
>
> This series adds a sysfs interface to control DAX kmem memory
> hotplug state, and refactors the memory_hotplug paths to make it
> possible for drivers to request an online type at hotplug time.
Gregory, slow down a bit please. I haven't even had the chance to go
through your replies on v1.
I'm currently on PTO and don't have the full day to review stuff :) And
boy oh boy, do I have a lot of stuff in my inbox.
Maybe given this is the second time the patch subject is suboptimal is
another sign to slow down a bit? :P
* Subject: [PATCH 0/8] dax/kmem: add runtime hotplug state control
* [PATCH v2 0/5] add runtime hotplug state control
I guess it should be "[PATCH v2 0/5] dax/kmem:add runtime hotplug state
control"
--
Cheers
David
Powered by blists - more mailing lists