From: sashiko-bot@kernel.org
To: "Jia Wang" <wangjia@ultrarisc.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/3] clk: composite: Export devm composite pdata helper
Date: Mon, 20 Jul 2026 00:48:13 +0000 [thread overview]
Message-ID: <20260720004814.58C611F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260720-ultrarisc-clock-v4-1-fe639d63bbac@ultrarisc.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Commit message inaccuracy: Non-devm pdata composite helpers are not actually exported, contradicting the commit message.
--
--- Patch [1]: [PATCH v4 1/3] clk: composite: Export devm composite pdata helper ---
commit 796e54251258da0c70103cd9b568babacd07c5ed
Author: Jia Wang <wangjia@ultrarisc.com>
clk: composite: Export devm composite pdata helper
Allow modular clock drivers to use devm_clk_hw_register_composite_pdata()
by exporting the helper.
> The non-devm composite helpers are already available to modules. Export
> this devm variant as well so users do not need to open-code devres
> cleanup.
[Severity: Medium]
Is this description accurate regarding the non-devm pdata helpers?
Looking at drivers/clk/clk-composite.c, the non-devm helper doesn't appear
to have an export annotation:
struct clk_hw *clk_hw_register_composite_pdata(struct device *dev,
const char *name,
const struct clk_parent_data *parent_data,
int num_parents,
struct clk_hw *mux_hw, const struct clk_ops *mux_ops,
struct clk_hw *rate_hw, const struct clk_ops *rate_ops,
struct clk_hw *gate_hw, const struct clk_ops *gate_ops,
unsigned long flags)
{
return __clk_hw_register_composite(dev, name, NULL, parent_data,
num_parents, mux_hw, mux_ops,
rate_hw, rate_ops, gate_hw,
gate_ops, flags);
}
Could the commit message be updated, or should the non-devm variants be
exported as well to match the description?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260720-ultrarisc-clock-v4-0-fe639d63bbac@ultrarisc.com?part=1
next prev parent reply other threads:[~2026-07-20 0:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 0:38 [PATCH v4 0/3] clk: ultrarisc: add DP1000 clock support Jia Wang via B4 Relay
2026-07-20 0:38 ` Jia Wang
2026-07-20 0:38 ` [PATCH v4 1/3] clk: composite: Export devm composite pdata helper Jia Wang via B4 Relay
2026-07-20 0:38 ` Jia Wang
2026-07-20 0:48 ` sashiko-bot [this message]
2026-07-20 0:38 ` [PATCH v4 2/3] dt-bindings: clock: ultrarisc: Add DP1000 Clock Controller Jia Wang via B4 Relay
2026-07-20 0:38 ` Jia Wang
2026-07-20 0:38 ` [PATCH v4 3/3] clk: ultrarisc: Add DP1000 clock driver Jia Wang via B4 Relay
2026-07-20 0:38 ` Jia Wang
2026-07-21 21:45 ` Brian Masney
2026-07-21 21:45 ` [PATCH v4 0/3] clk: ultrarisc: add DP1000 clock support Brian Masney
2026-07-22 0:15 ` Jia Wang
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=20260720004814.58C611F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wangjia@ultrarisc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.