From: Randy Dunlap <rdunlap@infradead.org>
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, alison.schofield@intel.com,
vishal.l.verma@intel.com, ira.weiny@intel.com,
dan.j.williams@intel.com, corbet@lwn.net
Subject: Re: [PATCH v2] Documentation/driver-api/cxl: device hotplug section
Date: Thu, 18 Dec 2025 12:22:05 -0800 [thread overview]
Message-ID: <e57020af-1124-4f71-afeb-681cc4122260@infradead.org> (raw)
In-Reply-To: <aURhZQalIBu8-KhR@gourry-fedora-PF4VCD3F>
On 12/18/25 12:17 PM, Gregory Price wrote:
> On Thu, Dec 18, 2025 at 11:36:41AM -0800, Randy Dunlap wrote:
>>> +To add or remove a device to/from an existing HDM-applied interleaved region,
>>> +that region must be torn down an re-created.
>>
>> ^s/an/and/
> doh.
>>
>> and one note: There are several places where you use one asterisk for emphasis,
>> e.g., *statically*. This means <italic> in Sphinx/ReST. If you happen
>> to mean/want bold, then use **bold text** (double asterisks).
>>
>
> I did intend italics, but if you think it should be bold instead given
> the contents, happy to change it.
No, it's fine as is. Just checking.
--
~Randy
next prev parent reply other threads:[~2025-12-18 20:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 17:07 [PATCH v2] Documentation/driver-api/cxl: device hotplug section Gregory Price
2025-12-18 19:36 ` Randy Dunlap
2025-12-18 20:17 ` Gregory Price
2025-12-18 20:22 ` Randy Dunlap [this message]
2025-12-19 10:55 ` Jonathan Cameron
2025-12-19 14:31 ` Gregory Price
2025-12-19 14:50 ` Jonathan Cameron
2025-12-19 15:06 ` Alejandro Lucero Palau
2025-12-19 15:55 ` Gregory Price
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=e57020af-1124-4f71-afeb-681cc4122260@infradead.org \
--to=rdunlap@infradead.org \
--cc=alison.schofield@intel.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=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