From: Dave Jiang <dave.jiang@intel.com>
To: Vishal Aslot <vaslot@nvidia.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Li Ming <ming.li@zohomail.com>,
Peter Zijlstra <peterz@infradead.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Zijun Hu <zijun.hu@oss.qualcomm.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cxl/hdm: allow zero sized committed decoders
Date: Wed, 1 Oct 2025 14:28:39 -0700 [thread overview]
Message-ID: <cb300580-1297-4d4b-9a3a-2cf7445b739b@intel.com> (raw)
In-Reply-To: <SN7PR12MB81316C958DF0F4B10369B928BBE6A@SN7PR12MB8131.namprd12.prod.outlook.com>
On 10/1/25 1:37 PM, Vishal Aslot wrote:
> Signed-off-by: Vishal Aslot <vaslot@nvidia.com>
Missing commit log?
> ---
> drivers/cxl/core/hdm.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cxl/core/hdm.c b/drivers/cxl/core/hdm.c
> index e9e1d555cec6..97a5f27f5b72 100644
> --- a/drivers/cxl/core/hdm.c
> +++ b/drivers/cxl/core/hdm.c
> @@ -1,5 +1,5 @@
> // SPDX-License-Identifier: GPL-2.0-only
> -/* Copyright(c) 2022 Intel Corporation. All rights reserved. */
> +/* Copyright(c) 2022-2025 Intel Corporation. All rights reserved. */
Stray change?
> #include <linux/seq_file.h>
> #include <linux/device.h>
> #include <linux/delay.h>
> @@ -1050,7 +1050,7 @@ static int init_hdm_decoder(struct cxl_port *port, struct cxl_decoder *cxld,
> dev_warn(&port->dev,
> "decoder%d.%d: Committed with zero size\n",
> port->id, cxld->id);
I wonder if we should make this dev_dbg() now that it's a valid case.
> - return -ENXIO;
> + return -ENOSPC;
> }
> port->commit_end = cxld->id;
> } else {
> @@ -1210,6 +1210,11 @@ int devm_cxl_enumerate_decoders(struct cxl_hdm *cxlhdm,
> rc = init_hdm_decoder(port, cxld, target_map, hdm, i,
> &dpa_base, info);
> if (rc) {
> + if (rc == -ENOSPC) {
> + put_device(&cxld->dev);
Why put_device()? Should we enumerate this decoder instead of pretend it doesn't exist? essentially only a dev_set_name() and device_add()?
> + rc = 0;
Don't think this is needed since the continue will put it at start of the loop where rc gets written by init_hdm_decoder() return value.
> + continue;
> + }
> dev_warn(&port->dev,
> "Failed to initialize decoder%d.%d\n",
> port->id, i);
> --
> 2.34.1
next prev parent reply other threads:[~2025-10-01 21:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 20:37 Vishal Aslot
2025-10-01 21:28 ` Dave Jiang [this message]
2025-10-01 22:03 ` Vishal Aslot
2025-10-01 22:46 ` Dave Jiang
2025-10-02 1:57 ` Vishal Aslot
2025-10-03 0:59 ` [PATCH v2] " Vishal Aslot
2025-10-03 4:28 ` Gregory Price
2025-10-04 13:30 ` Vishal Aslot
2025-10-03 16:20 ` Dave Jiang
2025-10-03 20:02 ` Vishal Aslot
2025-10-04 0:06 ` Davidlohr Bueso
2025-10-04 13:34 ` Vishal Aslot
2025-10-02 5:48 ` [PATCH] " Gregory Price
2025-10-02 15:32 ` Dave Jiang
2025-10-03 1:03 ` Vishal Aslot
2025-10-03 14:23 ` Gregory Price
2025-10-04 13:49 ` Vishal Aslot
2025-10-06 17:06 ` Gregory Price
2025-10-03 16:14 ` Dave Jiang
2025-10-04 14:05 ` Vishal Aslot
2025-10-06 14:54 ` 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=cb300580-1297-4d4b-9a3a-2cf7445b739b@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.carpenter@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=peterz@infradead.org \
--cc=vaslot@nvidia.com \
--cc=vishal.l.verma@intel.com \
--cc=zijun.hu@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®