From: Gregory Price <gourry@gourry.net>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: linux-cxl@vger.kernel.org, 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, kernel-team@meta.com
Subject: Re: [RFC DOC] cxl driver draft doc
Date: Tue, 29 Apr 2025 12:13:56 -0400 [thread overview]
Message-ID: <aBD6xEmzgTbT58kH@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20250429155927.2t4rdawgpf4veaq7@offworld>
On Tue, Apr 29, 2025 at 08:59:27AM -0700, Davidlohr Bueso wrote:
> On Sun, 27 Apr 2025, Gregory Price wrote:
>
> > This is one piece of cxl boot-to-bash series being documented here:
> > https://github.com/gourryinverse/cxl-boot-to-bash
> >
> > This page specifically:
> > https://gourryinverse.github.io/cxl-boot-to-bash/linux/cxl-driver/
>
> May I suggest using cxl.docs.kernel.org? I set that up years ago
> exactly for something like your writings, but never got around
> to it.
>
> Thanks,
> Davidlohr
That's one option, but we discussed just yeeting this into
linux/Documentation as "theory of operation". Dan seemed to favor this.
I'm just about done my full first draft, and it's turning out to around
60-ish pages when compiled down to a single HTML page (~12000 words).
I was planning to submit a patch series that updates with each single
page to make it more easily reviewable for the group.
~Gregory
prev parent reply other threads:[~2025-04-29 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 17:00 [RFC DOC] cxl driver draft doc Gregory Price
2025-04-29 15:59 ` Davidlohr Bueso
2025-04-29 16:13 ` Gregory Price [this message]
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=aBD6xEmzgTbT58kH@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=kernel-team@meta.com \
--cc=linux-cxl@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