From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Robert Richter <rrichter@amd.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
"Davidlohr Bueso" <dave@stgolabs.net>,
Jonathan Corbet <corbet@lwn.net>, <linux-cxl@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Gregory Price <gourry@gourry.net>,
"Fabio M. De Francesco" <fabio.m.de.francesco@linux.intel.com>,
Terry Bowman <terry.bowman@amd.com>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
<linux-doc@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] cxl, doc: Moving conventions in separate files
Date: Wed, 14 Jan 2026 17:31:08 +0000 [thread overview]
Message-ID: <20260114173108.00001eaa@huawei.com> (raw)
In-Reply-To: <20260112111707.794526-2-rrichter@amd.com>
On Mon, 12 Jan 2026 12:16:44 +0100
Robert Richter <rrichter@amd.com> wrote:
> Moving conventions in separate files.
>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> Signed-off-by: Robert Richter <rrichter@amd.com>
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
next prev parent reply other threads:[~2026-01-14 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 11:16 [PATCH v3 1/3] cxl, doc: Remove isonum.txt inclusion Robert Richter
2026-01-12 11:16 ` [PATCH v3 2/3] cxl, doc: Moving conventions in separate files Robert Richter
2026-01-14 17:31 ` Jonathan Cameron [this message]
2026-01-14 17:39 ` Alison Schofield
2026-01-12 11:16 ` [PATCH v3 3/3] Documentation/driver-api/cxl: ACPI PRM Address Translation Support and AMD Zen5 enablement Robert Richter
2026-01-13 22:03 ` Dave Jiang
2026-01-14 17:40 ` Alison Schofield
2026-01-14 18:00 ` Jonathan Cameron
2026-01-14 18:18 ` Gregory Price
2026-01-14 18:18 ` dan.j.williams
2026-01-14 17:27 ` [PATCH v3 1/3] cxl, doc: Remove isonum.txt inclusion Jonathan Cameron
2026-01-14 17:38 ` Alison Schofield
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=20260114173108.00001eaa@huawei.com \
--to=jonathan.cameron@huawei.com \
--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=fabio.m.de.francesco@linux.intel.com \
--cc=gourry@gourry.net \
--cc=ira.weiny@intel.com \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rrichter@amd.com \
--cc=terry.bowman@amd.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