[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aV9DxzUfDzX1rtQO@aschofie-mobl2.lan>
Date: Wed, 7 Jan 2026 21:42:31 -0800
From: Alison Schofield <alison.schofield@...el.com>
To: Gregory Price <gourry@...rry.net>
CC: <linux-cxl@...r.kernel.org>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <kernel-team@...a.com>, <dave@...olabs.net>,
<jonathan.cameron@...wei.com>, <dave.jiang@...el.com>,
<vishal.l.verma@...el.com>, <ira.weiny@...el.com>,
<dan.j.williams@...el.com>, <corbet@....net>, <rakuram.e96@...il.com>,
<alucerop@....com>
Subject: Re: [PATCH v3 2/2] Documentation/driver-api/cxl: device hotplug
section
On Wed, Jan 07, 2026 at 10:54:16AM -0500, Gregory Price wrote:
> On Tue, Jan 06, 2026 at 06:19:28PM -0800, Alison Schofield wrote:
> > On Fri, Dec 19, 2025 at 12:05:38PM -0500, Gregory Price wrote:
> > > Describe cxl memory device hotplug implications, in particular how the
> > > platform CEDT CFMWS must be described to support successful hot-add of
> > > memory devices.
> >
> > Who is the intended audience for this doc?
> >
> > Maybe it's already in another section not being edited, but I'd
> > expect to see CXL spec references.
> >
I'm fine with this merged. I starting to read it as more prescriptive
than it is wanting to be. It drives home the point that "You can't add
memory you haven't described in some way since the beginning of time".
Reviewed-by: Alison Schofield <alison.schofield@...el.com>
snip
Powered by blists - more mailing lists