From: Jonathan Cameron <jonathan.cameron@huawei.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>,
"Alison Schofield" <alison.schofield@intel.com>
Subject: Re: [PATCH v2 2/3] cxl: export internal structs for external Type2 drivers
Date: Fri, 27 Feb 2026 12:21:44 +0000 [thread overview]
Message-ID: <20260227122144.00007cc0@huawei.com> (raw)
In-Reply-To: <20260225121430.3839189-3-alejandro.lucero-palau@amd.com>
On Wed, 25 Feb 2026 12:14:29 +0000
alejandro.lucero-palau@amd.com wrote:
> From: Alejandro Lucero <alucerop@amd.com>
>
> In preparation for type2 support, move structs and functions a type2
> driver will need to access to into a new shared header file.
>
> Differentiate between public and private data to be preserved by type2
> drivers.
>
> Signed-off-by: Alejandro Lucero <alucerop@amd.com>
> Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> Tested-by: Alison Schofield <alison.schofield@intel.com>
> ---
> drivers/cxl/cxl.h | 97 +------------------
> drivers/cxl/cxlmem.h | 114 ----------------------
> include/cxl/cxl.h | 226 +++++++++++++++++++++++++++++++++++++++++++
I'm a tiny bit dubious that this has 'yet' reached the state where the copyright
notice in cxl.h is appropriate. This patch for instance is just code movement
which I'd not consider sufficient.
Meh, it'll be valid in the end!
Trivial follow through from the earlier patch.
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
> diff --git a/include/cxl/cxl.h b/include/cxl/cxl.h
> new file mode 100644
> index 000000000000..11f76d61c9f1
> --- /dev/null
> +++ b/include/cxl/cxl.h
> +/**
> + * cxl_dev_state_create - safely create and cast a cxl dev state embedded in a
> + * driver specific struct.
> + *
> + * @parent: device behind the request
> + * @type: CXL device type
> + * @serial: device identification
> + * @dvsec: dvsec capability offset
> + * @drv_struct: driver struct embedding a cxl_dev_state struct
> + * @member: drv_struct member as cxl_dev_state
Follow through from previous...
> + * @mbox: true if mailbox supported
> + *
next prev parent reply other threads:[~2026-02-27 12:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 12:14 [PATCH v2 0/3] type2 support preparation alejandro.lucero-palau
2026-02-25 12:14 ` [PATCH v2 1/3] cxl: support Type2 when initializing cxl_dev_state alejandro.lucero-palau
2026-02-25 15:43 ` Gregory Price
2026-02-27 19:54 ` Alejandro Lucero Palau
2026-02-27 12:14 ` Jonathan Cameron
2026-02-27 20:00 ` Alejandro Lucero Palau
2026-02-25 12:14 ` [PATCH v2 2/3] cxl: export internal structs for external Type2 drivers alejandro.lucero-palau
2026-02-25 15:35 ` Gregory Price
2026-02-27 19:53 ` Alejandro Lucero Palau
2026-02-27 12:21 ` Jonathan Cameron [this message]
2026-02-27 20:02 ` Alejandro Lucero Palau
2026-02-25 12:14 ` [PATCH v2 3/3] cxl: Move pci generic code alejandro.lucero-palau
2026-02-25 16:00 ` Gregory Price
2026-02-27 19:59 ` Alejandro Lucero Palau
2026-02-27 23:07 ` Gregory Price
2026-02-27 12:24 ` Jonathan Cameron
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=20260227122144.00007cc0@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alejandro.lucero-palau@amd.com \
--cc=alison.schofield@intel.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