MAINTAINERS: Notify the "Device Memory" community of memory hotplug changes
PATCH 1/1 MAINTAINERS: Notify the "Device Memory" community of memory hotplug changes
The recent episode of a warning regression in memremap_pages() [1] highlights that relevant updates are being missed by folks that care about core ZONE_DEVICE changes. Yes, CXL folks should pay more attention to linux-mm@, but it also would not hurt to copy linux-cxl@, where most Device Memory folks hang out, on memory hotplug changes by default.
--- MAINTAINERS | 1 + 1 file changed, 1 insertion(+)
MAINTAINERS +1 -0
@@ -16426,6 +16426,7 @@ MEMORY HOT(UN)PLUG M: David Hildenbrand <[email protected]> M: Oscar Salvador <[email protected]> L: [email protected] +L: [email protected] S: Maintained F: Documentation/admin-guide/mm/memory-hotplug.rst F: Documentation/core-api/memory-hotplug.rst
base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
Signature · 1 line
2.51.1
Quoted 5 lines · Dan Williams
The recent episode of a warning regression in
memremap_pages()[1] highlights that relevant updates are being missed by folks that care about coreZONE_DEVICEchanges. Yes, CXL folks should pay more attention to linux-mm@, but it also would not hurt to copy linux-cxl@, where most Device Memory folks hang out, on memory hotplug changes by default.
In general, that patch set went upstream too quickly. Quickly as in: more review should have been done. But here we are.
I reviewed that patch of that patch set but missed this change ...
Signature · 3 lines
Cheers David
Quoted 6 lines · On Fri, 19 Dec 2025 16:03:27 -0800 Dan Williams <[email protected]>…
The recent episode of a warning regression in
memremap_pages()[1] highlights that relevant updates are being missed by folks that care about coreZONE_DEVICEchanges. Yes, CXL folks should pay more attention to linux-mm@, but it also would not hurt to copy linux-cxl@, where most Device Memory folks hang out, on memory hotplug changes by default.
Quoted 11 lines
Cc David Hildenbrand <[email protected]>Cc Oscar Salvador <[email protected]>Cc Davidlohr Bueso <[email protected]>Cc Jonathan Cameron <[email protected]>Cc Dave Jiang <[email protected]>Cc Alison Schofield <[email protected]>Cc Vishal Verma <[email protected]>Cc Ira Weiny <[email protected]>Cc John Groves <[email protected]>Signed-off-by Dan Williams <[email protected]>
Makes sense to me.
Quoted 18 lines
--- MAINTAINERS | 1 + 1 file changed, 1 insertion(+)MAINTAINERS +1
-0@@ -16426,6 +16426,7 @@ MEMORY HOT(UN)PLUG M: David Hildenbrand <[email protected]> M: Oscar Salvador <[email protected]> L: [email protected] +L: [email protected] S: Maintained F: Documentation/admin-guide/mm/memory-hotplug.rst F: Documentation/core-api/memory-hotplug.rstbase-commit:
8f0b4cce4481fb22653697cced8d0d04027cb1e8
Quoted 34 lines · Dan Williams
The recent episode of a warning regression in
memremap_pages()[1] highlights that relevant updates are being missed by folks that care about coreZONE_DEVICEchanges. Yes, CXL folks should pay more attention to linux-mm@, but it also would not hurt to copy linux-cxl@, where most Device Memory folks hang out, on memory hotplug changes by default.Cc David Hildenbrand <[email protected]>Cc Oscar Salvador <[email protected]>Cc Davidlohr Bueso <[email protected]>Cc Jonathan Cameron <[email protected]>Cc Dave Jiang <[email protected]>Cc Alison Schofield <[email protected]>Cc Vishal Verma <[email protected]>Cc Ira Weiny <[email protected]>Cc John Groves <[email protected]>Signed-off-by Dan Williams <[email protected]>--- MAINTAINERS | 1 + 1 file changed, 1 insertion(+)MAINTAINERS +1
-0@@ -16426,6 +16426,7 @@ MEMORY HOT(UN)PLUG M: David Hildenbrand <[email protected]> M: Oscar Salvador <[email protected]> L: [email protected] +L: [email protected] S: Maintained F: Documentation/admin-guide/mm/memory-hotplug.rst F: Documentation/core-api/memory-hotplug.rst
Quoted 4 lines
base-commit:
8f0b4cce4481fb22653697cced8d0d04027cb1e8Signature · 1 line
2.51.1