All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Masney <bmasney@redhat.com>
To: wangjia@ultrarisc.com
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] clk: composite: Export devm composite pdata helper
Date: Thu, 16 Jul 2026 13:50:27 -0400	[thread overview]
Message-ID: <alkZ45CDRc8DMSrc@redhat.com> (raw)
In-Reply-To: <20260714-ultrarisc-clock-v3-1-4b1ccaa26b37@ultrarisc.com>

On Tue, Jul 14, 2026 at 09:35:07AM +0800, Jia Wang via B4 Relay wrote:
> From: Jia Wang <wangjia@ultrarisc.com>
> 
> 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.
> 
> Signed-off-by: Jia Wang <wangjia@ultrarisc.com>

Reviewed-by: Brian Masney <bmasney@redhat.com>


  reply	other threads:[~2026-07-16 17:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  1:35 [PATCH v3 0/3] clk: ultrarisc: add DP1000 clock support Jia Wang via B4 Relay
2026-07-14  1:35 ` Jia Wang
2026-07-14  1:35 ` [PATCH v3 1/3] clk: composite: Export devm composite pdata helper Jia Wang via B4 Relay
2026-07-14  1:35   ` Jia Wang
2026-07-16 17:50   ` Brian Masney [this message]
2026-07-14  1:35 ` [PATCH v3 2/3] dt-bindings: clock: ultrarisc: Add DP1000 Clock Controller Jia Wang via B4 Relay
2026-07-14  1:35   ` Jia Wang
2026-07-14  1:35 ` [PATCH v3 3/3] clk: ultrarisc: Add DP1000 clock driver Jia Wang via B4 Relay
2026-07-14  1:35   ` Jia Wang
2026-07-16 18:17   ` Brian Masney

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=alkZ45CDRc8DMSrc@redhat.com \
    --to=bmasney@redhat.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --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.