From: Teshan Kannangara <tpk.teshan@gmail.com>
To: dave@stgolabs.net
Cc: jonathan.cameron@huawei.com, dave.jiang@intel.com,
alison.schofield@intel.com, vishal.l.verma@intel.com,
ira.weiny@intel.com, dan.j.williams@intel.com,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] cxl/acpi: Fix coding style issues in acpi.c
Date: Tue, 17 Mar 2026 17:43:41 +0530 [thread overview]
Message-ID: <ablFdTrypTz67N0D@the-machine> (raw)
Fix various coding style issues in drivers/cxl/acpi.c, including
indentation, line wrapping, macro alignment, cast formatting,
and conditional braces.
No functional changes.
Signed-off-by: Teshan Kannangara <tpk.teshan@gmail.com>
---
drivers/cxl/acpi.c | 26 +++++++++++++++++---------
1 file changed, 17 insertions(+), 9 deletions(-)
diff --git a/drivers/cxl/acpi.c b/drivers/cxl/acpi.c
index 127537628817..b54b962cf973 100644
--- a/drivers/cxl/acpi.c
+++ b/drivers/cxl/acpi.c
@@ -395,9 +395,16 @@ static void cxl_setup_extended_linear_cache(struct cxl_root_decoder *cxlrd)
cxlrd->cache_size = cache_size;
}
-DEFINE_FREE(put_cxlrd, struct cxl_root_decoder *,
- if (!IS_ERR_OR_NULL(_T)) put_device(&_T->cxlsd.cxld.dev))
-DEFINE_FREE(del_cxl_resource, struct resource *, if (_T) del_cxl_resource(_T))
+DEFINE_FREE
+(put_cxlrd, struct cxl_root_decoder *,
+if (!IS_ERR_OR_NULL(_T))
+ put_device(&_T->cxlsd.cxld.dev))
+
+DEFINE_FREE
+(del_cxl_resource, struct resource *,
+if (_T)
+ del_cxl_resource(_T))
+
static int __cxl_parse_cfmws(struct acpi_cedt_cfmws *cfmws,
struct cxl_cfmws_context *ctx)
{
@@ -419,8 +426,8 @@ static int __cxl_parse_cfmws(struct acpi_cedt_cfmws *cfmws,
if (rc)
return rc;
- struct resource *res __free(del_cxl_resource) = alloc_cxl_resource(
- cfmws->base_hpa, cfmws->window_size, ctx->id++);
+ struct resource *res __free(del_cxl_resource) =
+ alloc_cxl_resource(cfmws->base_hpa, cfmws->window_size, ctx->id++);
if (!res)
return -ENOMEM;
@@ -542,7 +549,7 @@ static int cxl_get_chbs_iter(union acpi_subtable_headers *header, void *arg,
struct cxl_chbs_context *ctx = arg;
struct acpi_cedt_chbs *chbs;
- chbs = (struct acpi_cedt_chbs *) header;
+ chbs = (struct acpi_cedt_chbs *)header;
if (chbs->cxl_version == ACPI_CEDT_CHBS_VERSION_CXL11 &&
chbs->length != ACPI_CEDT_CHBS_LENGTH_CXL11)
@@ -774,12 +781,12 @@ static void cxl_acpi_lock_reset_class(void *dev)
static void cxl_set_public_resource(struct resource *priv, struct resource *pub)
{
- priv->desc = (unsigned long) pub;
+ priv->desc = (unsigned long)pub;
}
static struct resource *cxl_get_public_resource(struct resource *priv)
{
- return (struct resource *) priv->desc;
+ return (struct resource *)(priv->desc);
}
static void remove_cxl_resources(void *data)
@@ -850,8 +857,9 @@ static int add_cxl_resources(struct resource *cxl_res)
remove_resource(next);
del_cxl_resource(next);
next = _next;
- } else
+ } else {
next->start = new->end + 1;
+ }
}
}
return 0;
--
2.53.0
next reply other threads:[~2026-03-17 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 12:13 Teshan Kannangara [this message]
2026-03-17 14:48 ` [PATCH] cxl/acpi: Fix coding style issues in acpi.c Dave Jiang
2026-03-17 17:59 ` Jonathan Cameron
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=ablFdTrypTz67N0D@the-machine \
--to=tpk.teshan@gmail.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@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=vishal.l.verma@intel.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