From: Gregory Price <gourry@gourry.net>
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 0/3] cxl region changes for Type2 support
Date: Tue, 24 Feb 2026 11:06:56 -0500 [thread overview]
Message-ID: <aZ3MoKZgs26C2PrZ@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20260224152645.3441489-1-alejandro.lucero-palau@amd.com>
On Tue, Feb 24, 2026 at 03:26:42PM +0000, alejandro.lucero-palau@amd.com wrote:
> From: Alejandro Lucero <alucerop@amd.com>
>
> In preparation for Type2 devices/drivers support, these next patches
> adapt the cxl region code for required Type2 functionality preserving
> current functionality.
>
> Alejandro Lucero (3):
> cxl: Make region type based on endpoint type
> cxl/region: Factor out interleave ways setup
> cxl/region: Factor out interleave granularity setup
>
> drivers/cxl/core/region.c | 87 +++++++++++++++++++++++++--------------
> 1 file changed, 56 insertions(+), 31 deletions(-)
>
I've been testing with these for a while - the additional lockdep is a
nice addition. So for series
Tested-by: Gregory Price <gourry@gourry.net>
prev parent reply other threads:[~2026-02-24 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 15:26 [PATCH v1 0/3] cxl region changes for Type2 support alejandro.lucero-palau
2026-02-24 15:26 ` [PATCH v1 1/3] cxl: Make region type based on endpoint type alejandro.lucero-palau
2026-02-24 16:04 ` Gregory Price
2026-02-24 15:26 ` [PATCH v1 2/3] cxl/region: Factor out interleave ways setup alejandro.lucero-palau
2026-02-24 15:54 ` Dave Jiang
2026-02-24 16:21 ` Alejandro Lucero Palau
2026-02-24 16:05 ` Gregory Price
2026-02-24 15:26 ` [PATCH v1 3/3] cxl/region: Factor out interleave granularity setup alejandro.lucero-palau
2026-02-24 16:06 ` Gregory Price
2026-02-24 16:13 ` Dave Jiang
2026-02-24 15:39 ` [PATCH v1 0/3] cxl region changes for Type2 support Dave Jiang
2026-02-24 16:20 ` Alejandro Lucero Palau
2026-02-24 16:06 ` 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=aZ3MoKZgs26C2PrZ@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--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