From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Dan Williams <dan.j.williams@intel.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-cxl@vger.kernel.org,
Oscar Salvador <osalvador@suse.de>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>, John Groves <John@Groves.net>
Subject: Re: [PATCH] MAINTAINERS: Notify the "Device Memory" community of memory hotplug changes
Date: Sun, 21 Dec 2025 10:26:03 +0100 [thread overview]
Message-ID: <ebe2b0e1-38fd-49be-bb10-af497abf78f7@kernel.org> (raw)
In-Reply-To: <20251220000327.3502994-1-dan.j.williams@intel.com>
On 12/20/25 01:03, Dan Williams wrote:
> 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.
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 ...
Acked-by: David Hildenbrand (Red Hat) <david@kernel.org>
--
Cheers
David
next prev parent reply other threads:[~2025-12-21 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 0:03 Dan Williams
2025-12-21 9:26 ` David Hildenbrand (Red Hat) [this message]
2025-12-22 12:12 ` Jonathan Cameron
2025-12-22 13:36 ` John Groves
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=ebe2b0e1-38fd-49be-bb10-af497abf78f7@kernel.org \
--to=david@kernel.org \
--cc=John@Groves.net \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=vishal.l.verma@intel.com \
/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