From: Stephen Boyd <sboyd@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Andy Gross" <agross@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
linux-arm-msm@vger.kernel.org,
"Michael Turquette" <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] clk: qcom: cbf-msm8996: Convert to platform remove callback returning void
Date: Mon, 09 Oct 2023 20:49:27 -0700 [thread overview]
Message-ID: <3da62b36856cea690afd22d4c1500d2b.sboyd@kernel.org> (raw)
In-Reply-To: <cghreaj25elndy3wfdqhetlpk3hswyu5hnvvzdhcoqbpj2kin7@lzfeshjoyxti>
Quoting Bjorn Andersson (2023-09-20 10:29:58)
> On Tue, Sep 12, 2023 at 08:53:43AM +0200, Uwe Kleine-König wrote:
> > Hello Stephen,
> >
> > On Mon, Sep 11, 2023 at 01:02:53PM -0700, Stephen Boyd wrote:
> > > Quoting Uwe Kleine-König (2023-09-11 08:15:48)
> > > > The .remove() callback for a platform driver returns an int which makes
> > > > many driver authors wrongly assume it's possible to do error handling by
> > > > returning an error code. However the value returned is ignored (apart
> > > > from emitting a warning) and this typically results in resource leaks.
> > > > To improve here there is a quest to make the remove callback return
> > > > void. In the first step of this quest all drivers are converted to
> > > > .remove_new() which already returns void. Eventually after all drivers
> > > > are converted, .remove_new() is renamed to .remove().
> > > >
> > > > qcom_msm8996_cbf_icc_remove() returned zero unconditionally. After
> > > > changing this function to return void instead, the driver can be
> > > > converted trivially to use .remove_new().
> > > >
> > > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > > ---
> > >
> > > Do you want to take this? Otherwise, I can apply it to fixes.
> >
> > if "you" == "Uwe Kleine-König": Please take it via your tree. There is
> > still much to do before the next synchronous step, so there is no urge.
> > If the patch goes in during the next merge window that's fine, too.
> >
>
> @Stephen, should I just pick this in the Qcom tree for 6.7 then?
>
Yes please.
next prev parent reply other threads:[~2023-10-10 3:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 15:15 [PATCH] clk: qcom: cbf-msm8996: Convert to platform remove callback returning void Uwe Kleine-König
2023-09-11 20:02 ` Stephen Boyd
2023-09-12 6:53 ` Uwe Kleine-König
2023-09-20 17:29 ` Bjorn Andersson
2023-10-10 3:49 ` Stephen Boyd [this message]
2023-10-20 15:50 ` Uwe Kleine-König
2023-10-21 15:58 ` Bjorn Andersson
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=3da62b36856cea690afd22d4c1500d2b.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=kernel@pengutronix.de \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=u.kleine-koenig@pengutronix.de \
/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