From: Krzysztof Kozlowski <krzk@kernel.org>
To: Qi Han <hanqi@vivo.com>,
linus.walleij@linaro.org, afaerber@suse.de, mani@kernel.org
Cc: linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-actions@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: actions: use devm_clk_get_enabled()
Date: Tue, 24 Jun 2025 10:15:22 +0200 [thread overview]
Message-ID: <b0463cf0-9fbe-4b7a-b1fc-bdfdbb6bc780@kernel.org> (raw)
In-Reply-To: <20250624062220.21997-1-hanqi@vivo.com>
On 24/06/2025 08:22, Qi Han wrote:
> Use devm_clk_get_enabled() to simplify the code.
>
> Change-Id: I0902c50e50db565381c65e8d8a7f1481e82b271a
Please run scripts/checkpatch.pl on the patches and fix reported
warnings. After that, run also 'scripts/checkpatch.pl --strict' on the
patches and (probably) fix more warnings. Some warnings can be ignored,
especially from --strict run, but the code here looks like it needs a
fix. Feel free to get in touch if the warning is not clear.
> Signed-off-by: Qi Han <hanqi@vivo.com>
> ---
> drivers/pinctrl/actions/pinctrl-owl.c | 11 ++---------
> 1 file changed, 2 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/pinctrl/actions/pinctrl-owl.c b/drivers/pinctrl/actions/pinctrl-owl.c
> index 86f3d5c69e36..a66739a27489 100644
> --- a/drivers/pinctrl/actions/pinctrl-owl.c
> +++ b/drivers/pinctrl/actions/pinctrl-owl.c
> @@ -941,18 +941,13 @@ int owl_pinctrl_probe(struct platform_device *pdev,
> return PTR_ERR(pctrl->base);
>
> /* enable GPIO/MFP clock */
> - pctrl->clk = devm_clk_get(&pdev->dev, NULL);
> + pctrl->clk = devm_clk_get_enabled(&pdev->dev, NULL);
> +
Why are you introducing whitespace changes?
Are you sure that you are not introducing same bugs as other vivo
patches? Do you understand the issue with this scripting work?
Best regards,
Krzysztof
prev parent reply other threads:[~2025-06-24 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 6:22 [PATCH] pinctrl: actions: use devm_clk_get_enabled() Qi Han
2025-06-24 8:15 ` Krzysztof Kozlowski [this message]
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=b0463cf0-9fbe-4b7a-b1fc-bdfdbb6bc780@kernel.org \
--to=krzk@kernel.org \
--cc=afaerber@suse.de \
--cc=hanqi@vivo.com \
--cc=linus.walleij@linaro.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
/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.