All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
	<linux-cxl@vger.kernel.org>, David Hildenbrand <david@kernel.org>,
	"Oscar Salvador" <osalvador@suse.de>,
	Davidlohr Bueso <dave@stgolabs.net>,
	"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: Mon, 22 Dec 2025 12:12:18 +0000	[thread overview]
Message-ID: <20251222121218.00000b1b@huawei.com> (raw)
In-Reply-To: <20251220000327.3502994-1-dan.j.williams@intel.com>

On Fri, 19 Dec 2025 16:03:27 -0800
Dan Williams <dan.j.williams@intel.com> 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.
> 
> Link: http://lore.kernel.org/20251219123717.39330-1-john@groves.net [1]
> Cc: David Hildenbrand <david@kernel.org>
> Cc: Oscar Salvador <osalvador@suse.de>
> Cc: Davidlohr Bueso <dave@stgolabs.net>
> Cc: Jonathan Cameron <jonathan.cameron@huawei.com>
> Cc: Dave Jiang <dave.jiang@intel.com>
> Cc: Alison Schofield <alison.schofield@intel.com>
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Cc: Ira Weiny <ira.weiny@intel.com>
> Cc: John Groves <John@Groves.net>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Makes sense to me.

Acked-by: Jonathan Cameron <jonathan.cameron@huawei.com>
 
> ---
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5b11839cba9d..076322fe91de 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -16426,6 +16426,7 @@ MEMORY HOT(UN)PLUG
>  M:	David Hildenbrand <david@kernel.org>
>  M:	Oscar Salvador <osalvador@suse.de>
>  L:	linux-mm@kvack.org
> +L:	linux-cxl@vger.kernel.org
>  S:	Maintained
>  F:	Documentation/admin-guide/mm/memory-hotplug.rst
>  F:	Documentation/core-api/memory-hotplug.rst
> 
> base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8


  parent reply	other threads:[~2025-12-22 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-20  0:03 [PATCH] MAINTAINERS: Notify the "Device Memory" community of memory hotplug changes Dan Williams
2025-12-21  9:26 ` David Hildenbrand (Red Hat)
2025-12-22 12:12 ` Jonathan Cameron [this message]
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=20251222121218.00000b1b@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --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=david@kernel.org \
    --cc=ira.weiny@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.