From: Vinod Koul <vkoul@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: linux-phy@lists.infradead.org
Subject: Re: [bug report] phy: qcom: Introduce M31 USB PHY driver
Date: Wed, 7 Feb 2024 10:10:06 +0100 [thread overview]
Message-ID: <ZcNI7lSPLUcUzpae@matsya> (raw)
In-Reply-To: <88e2b874-b82d-4b6f-b1c5-761a8d066020@moroto.mountain>
On 06-02-24, 13:22, Dan Carpenter wrote:
> The patch 08e49af50701: "phy: qcom: Introduce M31 USB PHY driver"
> from Aug 14, 2023 (linux-next), leads to the following Smatch static
> checker warning:
>
> drivers/phy/qualcomm/phy-qcom-m31.c:302 m31usb_phy_probe()
> warn: passing zero to 'PTR_ERR'
>
> drivers/phy/qualcomm/phy-qcom-m31.c
> 294
> 295 qphy->phy = devm_phy_create(dev, NULL, &m31usb_phy_gen_ops);
> 296 if (IS_ERR(qphy->phy))
> 297 return dev_err_probe(dev, PTR_ERR(qphy->phy),
> 298 "failed to create phy\n");
> 299
> 300 qphy->vreg = devm_regulator_get(dev, "vdda-phy");
> 301 if (IS_ERR(qphy->vreg))
> --> 302 return dev_err_probe(dev, PTR_ERR(qphy->phy),
> ^^^
> This should have been "qphy->vreg".
>
> 303 "failed to get vreg\n");
> 304
>
> I can't work out what happened here.
>
> This was fixed in commit 5f7cd740a6b6 ("phy: qcom: phy-qcom-m31: fix
> wrong pointer pass to PTR_ERR()") but somehow it got changed back. I've
> looked at the git log and I don't see how that happened...
I think there might have been merge issue b/w the change of error
message indentation and this patch, that is the only thing I can this
of...
I have picked this one again, thanks for reporting
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2024-02-07 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 10:22 [bug report] phy: qcom: Introduce M31 USB PHY driver Dan Carpenter
2024-02-07 9:10 ` Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 11:58 Dan Carpenter
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=ZcNI7lSPLUcUzpae@matsya \
--to=vkoul@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-phy@lists.infradead.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.