From: sashiko-bot@kernel.org
To: "Dave Jiang" <dave.jiang@intel.com>
Cc: linux-cxl@vger.kernel.org
Subject: Re: [PATCH v7 7/7] cxl/test: Add cxl_test accelerator driver
Date: Mon, 29 Jun 2026 22:23:51 +0000 [thread overview]
Message-ID: <20260629222352.56D991F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260629221104.3891733-8-dave.jiang@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The function `cxl_set_capacity` is called but is neither declared nor defined anywhere in the kernel source.
--
commit e5897ac16ebf5251d0c169fc17ca2e8cde0dd51b
Author: Dave Jiang <dave.jiang@intel.com>
cxl/test: Add cxl_test accelerator driver
Add a type2 accelerator mock driver for the platform device that simulates
a CXL type2 device. The driver exercises the same minimal API calls that
a real CXL type2 driver would utilize.
> diff --git a/tools/testing/cxl/test/accel.c b/tools/testing/cxl/test/accel.c
> new file mode 100644
> index 0000000000000..8e6f4687ca02a
> --- /dev/null
> +++ b/tools/testing/cxl/test/accel.c
> @@ -0,0 +1,66 @@
[ ... ]
> +static int cxl_mock_accel_probe(struct platform_device *pdev)
> +{
> + struct mock_cxl_accel *cxl_accel;
> + struct device *dev = &pdev->dev;
> + struct cxl_dev_state *cxlds;
> + struct cxl_memdev *cxlmd;
> + struct range mock_range;
> + int rc;
> +
> + cxl_accel = devm_cxl_dev_state_create(&pdev->dev, CXL_DEVTYPE_DEVMEM,
> + pdev->id + 1, 0,
> + struct mock_cxl_accel, cxlds,
> + false);
> + if (!cxl_accel)
> + return -ENOMEM;
> +
> + cxlds = &cxl_accel->cxlds;
> + cxlds->media_ready = true;
> + rc = cxl_set_capacity(cxlds, SZ_512M);
[Severity: Low]
Is cxl_set_capacity() defined in a different patch in this series?
It appears this function is neither declared nor defined in the tree. Calling
an undeclared function here causes an implicit declaration error and a linker
failure, breaking the build when compiling the CXL mock test module.
> + if (rc)
> + return rc;
> +
> + cxlmd = devm_cxl_probe_mem(cxlds, &mock_range);
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260629221104.3891733-1-dave.jiang@intel.com?part=7
next prev parent reply other threads:[~2026-06-29 22:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 22:10 [PATCH v7 0/7] cxl: Add CXL type2 accelerator support for cxl_test Dave Jiang
2026-06-29 22:10 ` [PATCH v7 1/7] cxl/test: Add test for module parameters Dave Jiang
2026-06-29 22:21 ` sashiko-bot
2026-06-30 17:21 ` Alison Schofield
2026-06-30 17:28 ` Dave Jiang
2026-06-29 22:10 ` [PATCH v7 2/7] cxl/test: Add type2 support for mock CFMWS0 Dave Jiang
2026-06-29 22:11 ` [PATCH v7 3/7] cxl/test: Refactor platform device enumerations Dave Jiang
2026-06-29 22:11 ` [PATCH v7 4/7] cxl/test: Add hierarchy enumeration support for type2 device Dave Jiang
2026-07-01 7:31 ` Li Ming
2026-07-01 14:53 ` Dave Jiang
2026-06-29 22:11 ` [PATCH v7 5/7] cxl/test: Propagate -ENOMEM on platform_device_alloc() failures Dave Jiang
2026-06-29 22:11 ` [PATCH v7 6/7] cxl/test: Fixup hdm init for auto region to support type2 Dave Jiang
2026-06-29 22:11 ` [PATCH v7 7/7] cxl/test: Add cxl_test accelerator driver Dave Jiang
2026-06-29 22:23 ` sashiko-bot [this message]
2026-06-30 17:23 ` [PATCH v7 0/7] cxl: Add CXL type2 accelerator support for cxl_test Alison Schofield
2026-06-30 20:50 ` 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=20260629222352.56D991F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dave.jiang@intel.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