public inbox for linux-cxl@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: alejandro.lucero-palau@amd.com, linux-cxl@vger.kernel.org,
	dan.j.williams@intel.com, gourry@gourry.net
Cc: Alejandro Lucero <alucerop@amd.com>
Subject: Re: [PATCH v4 0/4] type2 support preparation
Date: Mon, 16 Mar 2026 16:56:46 -0700	[thread overview]
Message-ID: <fce194f4-3fb9-4e7e-907f-e6ea14a3782b@intel.com> (raw)
In-Reply-To: <20260306164741.3796372-1-alejandro.lucero-palau@amd.com>



On 3/6/26 9:47 AM, alejandro.lucero-palau@amd.com wrote:
> From: Alejandro Lucero <alucerop@amd.com>
> 
> For facilitating the integration of type2 support, here it comes the
> first patches to be applied in preparation for impending type2 drivers.
> 
> FWIW, the first two patches are a split of first patch in v23, while the
> third patch is the third patch in v23.
> 
> Not sure if I should have added the review tags as the code has not
> changed, but maybe better a clean start.
> 
> v4 changes:
> 	- clarify code removal in patch 4
> 	- fix commit author in patch 4
> 
> v3 changes:
> 	- fix commit (Greg, Jonathan)
> 	- fix member field comment (Jonathan)
> 	- add patch for removing redundant call in moved code (Greg)
> 
> v2 changes:
> 	- fix nit (Allison)
> 	- rephrase commit (Allison)
> 
> Alejandro Lucero (3):
>   cxl: support Type2 when initializing cxl_dev_state
>   cxl: export internal structs for external Type2 drivers
>   cxl: Move pci generic code
> 
> Gregory Price (1):
>   cxl/pci: Remove redundant cxl_pci_find_port() call
> 
>  drivers/cxl/core/core.h      |   2 +
>  drivers/cxl/core/mbox.c      |  12 +-
>  drivers/cxl/core/memdev.c    |  24 ++++
>  drivers/cxl/core/pci.c       |  57 +++++++++
>  drivers/cxl/core/regs.c      |   1 -
>  drivers/cxl/cxl.h            |  99 +--------------
>  drivers/cxl/cxlmem.h         |  86 +------------
>  drivers/cxl/cxlpci.h         |  13 ++
>  drivers/cxl/pci.c            |  84 ++-----------
>  include/cxl/cxl.h            | 226 +++++++++++++++++++++++++++++++++++
>  tools/testing/cxl/test/mem.c |   3 +-
>  11 files changed, 338 insertions(+), 269 deletions(-)
>  create mode 100644 include/cxl/cxl.h
> 
> 
> base-commit: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f

Applied to cxl/next

58f28930c7fb cxl: Move pci generic code from cxl_pci to core/cxl_pci
005869886d1d cxl: export internal structs for external Type2 drivers
9a775c07bb04 cxl: support Type2 when initializing cxl_dev_state


      parent reply	other threads:[~2026-03-16 23:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 16:47 [PATCH v4 0/4] type2 support preparation alejandro.lucero-palau
2026-03-06 16:47 ` [PATCH v4 1/4] cxl: support Type2 when initializing cxl_dev_state alejandro.lucero-palau
2026-03-06 16:47 ` [PATCH v4 2/4] cxl: export internal structs for external Type2 drivers alejandro.lucero-palau
2026-03-06 16:47 ` [PATCH v4 3/4] cxl: Move pci generic code alejandro.lucero-palau
2026-03-06 16:47 ` [PATCH v4 4/4] cxl/pci: Remove redundant cxl_pci_find_port() call alejandro.lucero-palau
2026-03-06 18:45   ` Davidlohr Bueso
2026-03-16 23:56 ` Dave Jiang [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=fce194f4-3fb9-4e7e-907f-e6ea14a3782b@intel.com \
    --to=dave.jiang@intel.com \
    --cc=alejandro.lucero-palau@amd.com \
    --cc=alucerop@amd.com \
    --cc=dan.j.williams@intel.com \
    --cc=gourry@gourry.net \
    --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