From: sashiko-bot@kernel.org
To: alejandro.lucero-palau@amd.com
Cc: linux-cxl@vger.kernel.org
Subject: Re: [PATCH v28 3/5] cxl/sfc: Initialize dpa without a mailbox
Date: Fri, 19 Jun 2026 17:24:44 +0000 [thread overview]
Message-ID: <20260619172444.75ABB1F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260618181806.118745-4-alejandro.lucero-palau@amd.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Malformed kernel-doc comment with a literal '+' character due to a diff artifact.
--
commit e64a1b07e5313555ece5e23f49237b31b36182be
Author: Alejandro Lucero <alucerop@amd.com>
cxl/sfc: Initialize dpa without a mailbox
This commit allows a Type2 driver to initialize DPA by giving the size of its
volatile hardware partition, avoiding reliance on a mailbox identify command.
It moves related functions to memdev and adds the sfc driver as a client.
> diff --git a/drivers/cxl/core/memdev.c b/drivers/cxl/core/memdev.c
> index 33a3d2e7b13af..500f077f935df 100644
> --- a/drivers/cxl/core/memdev.c
> +++ b/drivers/cxl/core/memdev.c
[ ... ]
> @@ -594,6 +594,73 @@ bool is_cxl_memdev(const struct device *dev)
[ ... ]
> +/**
> + * cxl_set_capacity: initialize dpa by a driver without a mailbox.
> + *
> ++ * @cxlds: pointer to cxl_dev_state
[Severity: Low]
This isn't a bug, but it looks like a literal + character was accidentally
included in the kernel-doc block. Was this an artifact left over from a
rebase resolution?
> + * @capacity: device volatile memory size
> + */
> +int cxl_set_capacity(struct cxl_dev_state *cxlds, u64 capacity)
> +{
> + struct cxl_dpa_info range_info = {
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260618181806.118745-1-alejandro.lucero-palau@amd.com?part=3
next prev parent reply other threads:[~2026-06-19 17:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 18:18 [PATCH v28 0/5] Type2 device basic support alejandro.lucero-palau
2026-06-18 18:18 ` [PATCH v28 1/5] sfc: add cxl support alejandro.lucero-palau
2026-06-19 13:12 ` Edward Cree
2026-06-19 17:24 ` sashiko-bot
2026-06-18 18:18 ` [PATCH v28 2/5] cxl/sfc: Map cxl regs alejandro.lucero-palau
2026-06-19 13:14 ` Edward Cree
2026-06-19 17:24 ` sashiko-bot
2026-06-18 18:18 ` [PATCH v28 3/5] cxl/sfc: Initialize dpa without a mailbox alejandro.lucero-palau
2026-06-19 13:15 ` Edward Cree
2026-06-19 17:24 ` sashiko-bot [this message]
2026-06-18 18:18 ` [PATCH v28 4/5] sfc: obtain and map cxl range using devm_cxl_probe_mem alejandro.lucero-palau
2026-06-18 23:05 ` Dave Jiang
2026-06-19 13:20 ` Edward Cree
2026-06-19 17:24 ` sashiko-bot
2026-06-18 18:18 ` [PATCH v28 5/5] sfc: support pio mapping based on cxl alejandro.lucero-palau
2026-06-18 23:06 ` Dave Jiang
2026-06-19 13:23 ` Edward Cree
2026-06-19 17:24 ` sashiko-bot
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=20260619172444.75ABB1F00A3D@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