From: Alison Schofield <alison.schofield@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: <linux-cxl@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-team@meta.com>,
<dave@stgolabs.net>, <jonathan.cameron@huawei.com>,
<dave.jiang@intel.com>, <vishal.l.verma@intel.com>,
<ira.weiny@intel.com>, <dan.j.williams@intel.com>,
<corbet@lwn.net>, <rakuram.e96@gmail.com>, <alucerop@amd.com>
Subject: Re: [PATCH v3 2/2] Documentation/driver-api/cxl: device hotplug section
Date: Wed, 7 Jan 2026 21:42:31 -0800 [thread overview]
Message-ID: <aV9DxzUfDzX1rtQO@aschofie-mobl2.lan> (raw)
In-Reply-To: <aV6BqOarpY0PUt7h@gourry-fedora-PF4VCD3F>
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@intel.com>
snip
next prev parent reply other threads:[~2026-01-08 5:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 17:05 [PATCH v3 0/2] Documentation/driver-api/cxl: device hotplug Gregory Price
2025-12-19 17:05 ` [PATCH v3 1/2] Documentation/driver-api/cxl: BIOS/EFI expectation update Gregory Price
2025-12-19 17:28 ` Jonathan Cameron
2025-12-19 17:49 ` Gregory Price
2025-12-20 6:53 ` Alejandro Lucero Palau
2026-01-05 21:00 ` Dave Jiang
2025-12-19 17:05 ` [PATCH v3 2/2] Documentation/driver-api/cxl: device hotplug section Gregory Price
2025-12-20 6:56 ` Alejandro Lucero Palau
2026-01-05 21:10 ` Dave Jiang
2026-01-07 2:19 ` Alison Schofield
2026-01-07 15:54 ` Gregory Price
2026-01-08 5:42 ` Alison Schofield [this message]
2026-01-06 17:54 ` [PATCH v3 0/2] Documentation/driver-api/cxl: device hotplug Dave Jiang
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=aV9DxzUfDzX1rtQO@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=alucerop@amd.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=gourry@gourry.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=kernel-team@meta.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rakuram.e96@gmail.com \
--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