Linux CXL
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: <alejandro.lucero-palau@amd.com>
Cc: <linux-cxl@vger.kernel.org>, <dan.j.williams@intel.com>,
	<dave.jiang@intel.com>, Alejandro Lucero <alucerop@amd.com>
Subject: Re: [PATCH v1 2/3] cxl: export internal structs for external Type2 drivers
Date: Mon, 23 Feb 2026 18:50:23 -0800	[thread overview]
Message-ID: <aZ0R79N952TTsRcl@aschofie-mobl2.lan> (raw)
In-Reply-To: <20260223142633.2994082-3-alejandro.lucero-palau@amd.com>

On Mon, Feb 23, 2026 at 02:26:32PM +0000, alejandro.lucero-palau@amd.com wrote:
> From: Alejandro Lucero <alucerop@amd.com>
> 
> In preparation for type2 support, move structs and functions needed by
> external type2 drivers. Differentiate between public and private data to
> be preserved by type2 drivers.

I would have enjoyed a mention in the commit log of what was needed.
When I saw struct cxl_dpa_perf, struct cxl_dpa_partition,
CXL_NR_PARTITIONS_MAX, enum cxl_partition_mode, it wasn't so clear
why those were needed (as opposed to the cxl_dev_state defines)

I was a bit concerned that new cxl/cxl.h had dependencies, so tested
that it compiled all be itself in a completely separate module. 

Tested-by: Alison Schofield <alison.schofield@intel.com>


  parent reply	other threads:[~2026-02-24  2:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 14:26 [PATCH v1 0/3] type2 support preparation alejandro.lucero-palau
2026-02-23 14:26 ` [PATCH v1 1/3] cxl: support Type2 when initializing cxl_dev_state alejandro.lucero-palau
2026-02-24  0:19   ` Dave Jiang
2026-02-24  2:02   ` Alison Schofield
2026-02-24 16:30     ` Alejandro Lucero Palau
2026-02-23 14:26 ` [PATCH v1 2/3] cxl: export internal structs for external Type2 drivers alejandro.lucero-palau
2026-02-24  0:21   ` Dave Jiang
2026-02-24  2:50   ` Alison Schofield [this message]
2026-02-24 16:38     ` Alejandro Lucero Palau
2026-02-24 17:38       ` Alison Schofield
2026-02-25 12:05         ` Alejandro Lucero Palau
2026-02-23 14:26 ` [PATCH v1 3/3] cxl: Move pci generic code alejandro.lucero-palau
2026-02-24  0:27   ` 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=aZ0R79N952TTsRcl@aschofie-mobl2.lan \
    --to=alison.schofield@intel.com \
    --cc=alejandro.lucero-palau@amd.com \
    --cc=alucerop@amd.com \
    --cc=dan.j.williams@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