From: Brian Masney <bmasney@redhat.com>
To: Slavin Liu <bolin.liu@seu.edu.cn>
Cc: biju.das.jz@bp.renesas.com, sboyd@kernel.org,
bmasney+clk@redhat.com, jbrunet+clk@baylibre.com,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] clk: versaclock7: propagate all xin lookup failures
Date: Fri, 18 Sep 2026 18:21:06 -0400 [thread overview]
Message-ID: <aq25UlM87_UIatKW@redhat.com> (raw)
In-Reply-To: <20260911060918.94343-1-bolin.liu@seu.edu.cn>
Hi Slavin,
On Fri, Sep 11, 2026 at 02:09:18PM +0800, Slavin Liu wrote:
> The xin clock is used to obtain the APLL reference rate. Handle all
> lookup errors, not only probe deferral, before clk_get_rate() can see
> an error pointer.
>
> Detected by static analysis and reviewed with AI-assisted source auditing.
>
> Fixes: 48c5e98fedd9 ("clk: Renesas versaclock7 ccf device driver")
> Assisted-by: LLM
> Signed-off-by: Slavin Liu <bolin.liu@seu.edu.cn>
> ---
> drivers/clk/clk-versaclock7.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clk/clk-versaclock7.c b/drivers/clk/clk-versaclock7.c
> index 1340d2f512be..5f32d3fb807a 100644
> --- a/drivers/clk/clk-versaclock7.c
> +++ b/drivers/clk/clk-versaclock7.c
> @@ -1117,8 +1117,8 @@ static int vc7_probe(struct i2c_client *client)
> vc7->chip_info = i2c_get_match_data(client);
>
> vc7->pin_xin = devm_clk_get(&client->dev, "xin");
> - if (PTR_ERR(vc7->pin_xin) == -EPROBE_DEFER) {
> - return dev_err_probe(&client->dev, -EPROBE_DEFER,
> + if (IS_ERR(vc7->pin_xin)) {
> + return dev_err_probe(&client->dev, PTR_ERR(vc7->pin_xin),
> "xin not specified\n");
Could you clarify the error message as well? Perhaps 'devm_clk_get failed for
xin' ?
You can drop the PATCH RFC on the next version.
Brian
prev parent reply other threads:[~2026-09-18 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 6:09 Slavin Liu
2026-09-18 22:21 ` Brian Masney [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=aq25UlM87_UIatKW@redhat.com \
--to=bmasney@redhat.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=bmasney+clk@redhat.com \
--cc=bolin.liu@seu.edu.cn \
--cc=jbrunet+clk@baylibre.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®