From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kalle Valo <kvalo@codeaurora•org>,
Wireless <linux-wireless@vger•kernel.org>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Arend Van Spriel <arend.vanspriel@broadcom•com>
Subject: linux-next: build warning after merge of the wireless-drivers tree
Date: Fri, 16 Jun 2017 08:25:07 +1000 [thread overview]
Message-ID: <20170616082507.1e824796@canb.auug.org.au> (raw)
Hi all,
After merging the wireless-drivers tree, today's linux-next build
(x86_64 allmodconfig) produced this warning:
drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c: In function 'brcmf_usb_probe_phase2':
drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c:1198:2: warning: 'devinfo' may be used uninitialized in this function [-Wmaybe-uninitialized]
mutex_unlock(&devinfo->dev_init_lock);
^
Introduced by commit
6d0507a777fb ("brcmfmac: add parameter to pass error code in firmware callback")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-06-15 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 22:25 Stephen Rothwell [this message]
2017-06-16 5:07 ` linux-next: build warning after merge of the wireless-drivers tree Kalle Valo
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=20170616082507.1e824796@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=arend.vanspriel@broadcom$(echo .)com \
--cc=kvalo@codeaurora$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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