From: Dan Williams <dan.j.williams@intel.com>
To: Alison Schofield <alison.schofield@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <dave.jiang@intel.com>,
<Jonathan.Cameron@huawei.com>, <a.manzanares@samsung.com>
Subject: Re: [PATCH] Documentation: CXL Maturity Map
Date: Mon, 17 Jun 2024 15:38:58 -0700 [thread overview]
Message-ID: <6670bb0253a82_310129499@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <ZmEroVRLDDLdHIqL@aschofie-mobl2>
Alison Schofield wrote:
> On Fri, May 24, 2024 at 05:53:49PM -0700, Dan Williams wrote:
> > Provide a survey of the work-in-progress maturity (implementation
> > status) of various aspects of the CXL subsystem.
> >
> > Clarify that in addition to ongoing upkeep relative to specification
> > updates, there are some long running themes in the driver that respond
> > to the discovery of new corner cases (bugs) and new use cases (feature
> > extensions).
> >
> > The primary audience is distribution maintainers, but it also serves as
> > a guide for kernel developers to understand what aspects of the CXL
> > subsystem need more help. It is a landing page to document ongoing
> > progress, and a guide to discern exposure to work-in-progress features.
>
> Hi Dan,
>
> I'm wondering if Scan Media can be added to the list. I was within
> striking distance of posting that set when higher priority work called.
> Since it got pushed aside no one has cared :( I'd welcome the chance
> to contribute it upstream if there is a justification. Can we add it
> here as a [0] here to keep it on the radar.
Added.
next prev parent reply other threads:[~2024-06-17 22:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240617165830uscas1p12e867fc6ad52fa7cfa32955f3150dd6f@uscas1p1.samsung.com>
2024-05-25 0:53 ` [PATCH] Documentation: CXL Maturity Map Dan Williams
2024-06-06 3:23 ` Alison Schofield
2024-06-17 22:25 ` Davidlohr Bueso
2024-06-17 22:38 ` Dan Williams [this message]
2024-06-06 14:40 ` Jonathan Cameron
2024-06-17 22:50 ` Dan Williams
2024-06-20 17:45 ` Jonathan Cameron
2024-06-17 16:58 ` Adam Manzanares
2024-06-17 22:54 ` Dan Williams
2024-06-27 17:52 ` Adam Manzanares
2024-06-19 16:02 ` Alejandro Lucero Palau
2024-07-03 23:26 ` Dan Williams
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=6670bb0253a82_310129499@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
/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