Linux CXL
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: alejandro.lucero-palau@amd.com
Cc: linux-cxl@vger.kernel.org
Subject: Re: [PATCH v30 1/2] cxl: Support Type2 cxl regs mapping
Date: Mon, 29 Jun 2026 17:52:40 +0000	[thread overview]
Message-ID: <20260629175242.3AEC11F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260629183727.51502-2-alejandro.lucero-palau@amd.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit claims to export core functions for a Type2 driver to discover and map device registers, but it fails to expose the mapping functions in a public header.
--

commit e264e4eb8d1791f45613794c005249488536d8e2
Author: Alejandro Lucero <alucerop@amd.com>

cxl: Support Type2 cxl regs mapping

This commit creates a new public header file for CXL PCI definitions. It
exports the register setup function and register block identifier enum so
that out-of-subsystem Type2 drivers can discover device registers.

> Export cxl core functions for a Type2 driver being able to discover and
> map the device registers.

[ ... ]

> diff --git a/include/cxl/pci.h b/include/cxl/pci.h
> new file mode 100644
> index 0000000000000..3e0000015871a
> --- /dev/null
> +++ b/include/cxl/pci.h
> @@ -0,0 +1,22 @@

[ ... ]

> +struct cxl_register_map;
> +struct pci_dev;
> +
> +int cxl_pci_setup_regs(struct pci_dev *pdev, enum cxl_regloc_type type,
> +		       struct cxl_register_map *map);
> +#endif

[Severity: Medium]
The commit message mentions exporting functions to both discover and map device
registers, but are the mapping functions missing from this public header?

While cxl_pci_setup_regs() is exposed here for register discovery, the
functions needed to map those registers, cxl_map_component_regs() and
cxl_map_device_regs(), appear to remain unexported in the private
drivers/cxl/cxl.h header.

Does this regression prevent a Type 2 driver outside of drivers/cxl/ from
cleanly calling the mapping functions without duplicating prototypes or
violating subsystem boundaries?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260629183727.51502-1-alejandro.lucero-palau@amd.com?part=1

  reply	other threads:[~2026-06-29 17:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 18:37 [PATCH v30 0/2] Type2 device basic support alejandro.lucero-palau
2026-06-29 18:00 ` Dave Jiang
2026-06-29 18:37 ` [PATCH v30 1/2] cxl: Support Type2 cxl regs mapping alejandro.lucero-palau
2026-06-29 17:52   ` sashiko-bot [this message]
2026-06-29 18:37 ` [PATCH v30 2/2] cxl: Support dpa without a mailbox alejandro.lucero-palau
2026-06-30 20:49 ` [PATCH v30 0/2] Type2 device basic support 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=20260629175242.3AEC11F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=alejandro.lucero-palau@amd.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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