[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191211222829.GV50317@dtor-ws>
Date: Wed, 11 Dec 2019 14:28:29 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Marc Gonzalez <marc.w.gonzalez@...e.fr>
Cc: Robin Murphy <robin.murphy@....com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
Stephen Boyd <sboyd@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
LKML <linux-kernel@...r.kernel.org>,
Sudip Mukherjee <sudipm.mukherjee@...il.com>,
Russell King <rmk+kernel@...linux.org.uk>,
Guenter Roeck <linux@...ck-us.net>,
linux-clk <linux-clk@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v1] clk: Convert managed get functions to devm_add_action
API
On Wed, Dec 11, 2019 at 05:17:28PM +0100, Marc Gonzalez wrote:
> But I need to ask: what is the rationale for the devm_add_action API?
For one-off and maybe complex unwind actions in drivers that wish to use
devm API (as mixing devm and manual release is verboten). Also is often
used when some core subsystem does not provide enough devm APIs.
Thanks.
--
Dmitry
Powered by blists - more mailing lists