From: Larry Finger <Larry.Finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43legacy: fix "‘up_dev’ may be used uninitialized" warning
Date: Mon, 12 Jan 2009 14:11:52 -0600 [thread overview]
Message-ID: <496BA408.1080005@lwfinger.net> (raw)
In-Reply-To: <1231789741-13433-3-git-send-email-linville@tuxdriver.com>
John W. Linville wrote:
> drivers/net/wireless/b43legacy/main.c: In function =E2=80=98b43legacy=
_op_dev_config=E2=80=99:
> drivers/net/wireless/b43legacy/main.c:2468: warning: =E2=80=98up_dev=E2=
=80=99 may be used uninitialized in this function
>=20
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> ---
> drivers/net/wireless/b43legacy/main.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>=20
> diff --git a/drivers/net/wireless/b43legacy/main.c b/drivers/net/wire=
less/b43legacy/main.c
> index c1324e3..fb996c2 100644
> --- a/drivers/net/wireless/b43legacy/main.c
> +++ b/drivers/net/wireless/b43legacy/main.c
> @@ -2465,7 +2465,7 @@ static void b43legacy_put_phy_into_reset(struct=
b43legacy_wldev *dev)
> static int b43legacy_switch_phymode(struct b43legacy_wl *wl,
> unsigned int new_mode)
> {
> - struct b43legacy_wldev *up_dev;
> + struct b43legacy_wldev *uninitialized_var(up_dev);
> struct b43legacy_wldev *down_dev;
> int err;
> bool gmode =3D 0;
It seems that some versions of gcc don't do the flow analysis
correctly, so
ACK
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-01-12 20:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 19:48 [PATCH] mac80211: fix "‘ret’ may be used uninitialized" warning John W. Linville
2009-01-12 19:48 ` [PATCH] b43: fix "‘gmode’ " John W. Linville
2009-01-12 19:48 ` [PATCH] b43legacy: fix "‘up_dev’ " John W. Linville
2009-01-12 19:49 ` [PATCH] iwl3945: fix "‘power_idx’ " John W. Linville
2009-01-12 19:49 ` [PATCH] p54: fix "‘ret’ " John W. Linville
2009-01-12 20:47 ` Christian Lamparter
2009-01-12 21:35 ` [PATCH] iwl3945: fix "‘power_idx’ " reinette chatre
2009-01-12 20:11 ` [PATCH] b43legacy: fix "‘up_dev’ " Michael Buesch
2009-01-12 20:11 ` Larry Finger [this message]
2009-01-12 20:09 ` [PATCH] b43: fix "‘gmode’ " Michael Buesch
2009-01-12 20:10 ` Larry Finger
2009-01-12 20:17 ` John W. Linville
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=496BA408.1080005@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).