From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 96FAEC433EF for ; Thu, 17 Feb 2022 20:26:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1343591AbiBQU0r (ORCPT ); Thu, 17 Feb 2022 15:26:47 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:35080 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1343588AbiBQU0o (ORCPT ); Thu, 17 Feb 2022 15:26:44 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 675DBDF0A; Thu, 17 Feb 2022 12:26:28 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id DCD01B821B1; Thu, 17 Feb 2022 20:26:26 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9B8C5C340EB; Thu, 17 Feb 2022 20:26:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1645129585; bh=+s2dZtudwLbzmAWO5qcLZKAFd2wPQHJgj58H0Wg9CWQ=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=gWgVAkGnjWRWFIDBYhBFwIM1ddEEjBGo+zZEai0RCTE2YNo7JDfAIDXD7F/mON6l+ Br8ehSXVr2Cm0X4KmrE0sUwOMkZur4rVS9hhjxThS12JG399ZIUTNCwpg1iLhlOWHU wIFrmIMbdoZMsUXQXY8o7ag5zarY8yDNyDHOzk/CKwM16wsQjo+JkSnGA4joExxyh/ BY+CCLFq173ByNFsTguiMa49MbrxO6TKydIiW34UKWDfWN6sHt221U23MSpTDUcyoB HGMUOhN1hiQLF3Uyp08Bu6V/+Faf5QWY7sxrEABMMhMty4L+z8a0zpRIr1hG9KMJgW cJQ2to6HKUIPA== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20220208124034.414635-19-wenst@chromium.org> References: <20220208124034.414635-1-wenst@chromium.org> <20220208124034.414635-19-wenst@chromium.org> Subject: Re: [PATCH v3 18/31] clk: mediatek: Implement mtk_clk_unregister_composites() API From: Stephen Boyd Cc: Chen-Yu Tsai , Chun-Jie Chen , AngeloGioacchino Del Regno , Miles Chen , linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org To: Chen-Yu Tsai , Matthias Brugger , Michael Turquette Date: Thu, 17 Feb 2022 12:26:24 -0800 User-Agent: alot/0.10 Message-Id: <20220217202625.9B8C5C340EB@smtp.kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Chen-Yu Tsai (2022-02-08 04:40:21) > mtk_clk_register_composites(), as the name suggests, is used to register > a given list of composite clks. However it is lacking a counterpart > unregister API. >=20 > Implement said unregister API so that the various clock platform drivers > can utilize it to do proper unregistration, cleanup and removal. >=20 > In the header file, the register function's declaration is also > reformatted to fit code style guidelines. >=20 > Signed-off-by: Chen-Yu Tsai > Reviewed-by: AngeloGioacchino Del Regno > Reviewed-by: Miles Chen > --- Applied to clk-next