Search Linux Wireless

Question on compiler warning

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



In his regular article entitled Build regressions/improvements in v3.13-rc6" (http://lkml.indiana.edu/hypermail/linux/kernel/1312.3/01550.html), Geert Uytterhoeven reports the following warning regression:

+ /scratch/kisskb/src/drivers/net/wireless/b43/phy_n.c: warning: 'val_addr' may be used uninitialized in this function [-Wuninitialized]: => 178:21

This warning does not show up on any of my compilers, and it should not as the initialization and usage of that variable both take place in conditional branches that are testing exactly the same pointer.

Despite the fact that the warning is bogus, should a patch be submitted to clear it? I lean toward "no" as an answer because that would mask the warning if there were some future change that screwed up the flow; however, I wanted to check with the community.

Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux