From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Srinath Mannam <srinath.mannam@broadcom.com>
Subject: linux-next: build warning after merge of the phy-next tree
Date: Thu, 28 Mar 2019 11:29:25 +1100 [thread overview]
Message-ID: <20190328112925.0fbe34e2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
Hi Kishon,
After merging the phy-next tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
In file included from include/linux/phy/phy.h:19,
from drivers/phy/broadcom/phy-bcm-sr-usb.c:10:
drivers/phy/broadcom/phy-bcm-sr-usb.c: In function 'bcm_usb_phy_probe':
include/linux/device.h:1138:19: warning: 'phy_cfg' may be used uninitialized in this function [-Wmaybe-uninitialized]
dev->driver_data = data;
~~~~~~~~~~~~~~~~~^~~~~~
drivers/phy/broadcom/phy-bcm-sr-usb.c:289:26: note: 'phy_cfg' was declared here
struct bcm_usb_phy_cfg *phy_cfg;
^~~~~~~
Introduced by commit
a3b96057577c ("phy: sr-usb: Add Stingray USB PHY driver")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-03-28 0:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 0:29 Stephen Rothwell [this message]
2019-03-28 3:03 ` linux-next: build warning after merge of the phy-next tree Srinath Mannam
-- strict thread matches above, loose matches on Subject: below --
2020-01-07 5:17 Stephen Rothwell
2020-01-07 5:26 ` Ramuthevar, Vadivel MuruganX
2017-08-22 5:07 Stephen Rothwell
2017-08-24 5:23 ` Stephen Rothwell
2017-08-24 8:01 ` Kishon Vijay Abraham I
2016-11-16 3:00 Stephen Rothwell
2016-11-16 13:28 ` wlf
2016-11-16 16:39 ` Kishon Vijay Abraham I
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=20190328112925.0fbe34e2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=srinath.mannam@broadcom.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;
as well as URLs for NNTP newsgroup(s).