From: Vinod Koul <vkoul@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Kishon <kishon@ti.com>, Heiko Stuebner <heiko@sntech.de>,
Zhang Yubing <yubing.zhang@rock-chips.com>,
Frank Wang <frank.wang@rock-chips.com>
Subject: Re: [phy:next 32/34] drivers/phy/rockchip/phy-rockchip-usbdp.c:1292:6: warning: variable 'ret' is used uninitialized whenever 'if' condition is true
Date: Mon, 15 Apr 2024 13:05:55 +0530 [thread overview]
Message-ID: <ZhzY2-dN51EO03Tg@matsya> (raw)
In-Reply-To: <x2ons6nqwuj4a56eskuf53n6736cmvjup3lxds7ngpnm6bte25@4tqfnkjg7okh>
On 14-04-24, 18:05, Sebastian Reichel wrote:
> Hello Vinod,
>
> On Sun, Apr 14, 2024 at 10:31:04AM +0800, kernel test robot wrote:
> > >> drivers/phy/rockchip/phy-rockchip-usbdp.c:1292:6: warning: variable 'ret' is used uninitialized whenever '||' condition is true [-Wsometimes-uninitialized]
> > 1292 | if (!(udphy->mode & UDPHY_MODE_USB) || udphy->hs) {
> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> [...]
>
> > vim +1292 drivers/phy/rockchip/phy-rockchip-usbdp.c
> >
> > 1284
> > 1285 static int rk_udphy_usb3_phy_init(struct phy *phy)
> > 1286 {
> > 1287 struct rk_udphy *udphy = phy_get_drvdata(phy);
> > 1288 int ret;
>
> I dropped the '= 0;' by your request. Based on the upper bug
> report I will just send a patch readding it. Is that fine
> with you?
Yeah I missed the goto statement which would require this..
Btw looking at the code again, why would we not power on the phy in case
of DP or hig speed?
Btw, yes patch to fix would be welcome
--
~Vinod
next prev parent reply other threads:[~2024-04-15 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 2:31 [phy:next 32/34] drivers/phy/rockchip/phy-rockchip-usbdp.c:1292:6: warning: variable 'ret' is used uninitialized whenever 'if' condition is true kernel test robot
2024-04-14 16:05 ` Sebastian Reichel
2024-04-15 7:35 ` Vinod Koul [this message]
2024-04-15 9:02 ` Sebastian Reichel
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=ZhzY2-dN51EO03Tg@matsya \
--to=vkoul@kernel.org \
--cc=frank.wang@rock-chips.com \
--cc=heiko@sntech.de \
--cc=kishon@ti.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sebastian.reichel@collabora.com \
--cc=yubing.zhang@rock-chips.com \
/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