On Fri, 2010-05-28 at 13:34 -0400, John W. Linville wrote: > On Thu, May 27, 2010 at 02:14:54PM -0400, Prarit Bhargava wrote: > > Fixes 'make -j24 CONFIG_DEBUG_SECTION_MISMATCH=y' warning: > > > > drivers/net/wireless/ath/ath9k/eeprom_4k.c: In function ‘ath9k_hw_get_4k_gain_boundaries_pdadcs.clone.1’: > > drivers/net/wireless/ath/ath9k/eeprom_4k.c:311: error: ‘minPwrT4’ may be used uninitialized in this function > > drivers/net/wireless/ath/ath9k/eeprom_9287.c: In function ‘ath9k_hw_get_AR9287_gain_boundaries_pdadcs’: > > drivers/net/wireless/ath/ath9k/eeprom_9287.c:302: error: ‘minPwrT4’ may be used uninitialized in this function > > drivers/net/wireless/ath/ath9k/eeprom_def.c: In function ‘ath9k_hw_get_def_gain_boundaries_pdadcs.clone.0’: > > drivers/net/wireless/ath/ath9k/eeprom_def.c:679: error: ‘minPwrT4’ may be used uninitialized in this function > > > > Signed-off-by: Prarit Bhargava <prarit@xxxxxxxxxx> > > It looks to me like minPwrT4 will get initialized as long as > numXpdGains is non-zero in all cases. Anyone know if this is true? It's calculated based on a value from EEPROM (xpdMask). If xpdMask is 0, numXpdGain would be 0. So bogus EEPROM can lead to bogus tMinCalPower. But the good thing is that tMinCalPower is never used. So let's just eliminate tMinCalPower in all three files, as well as the corresponding function arguments. -- Regards, Pavel Roskin -- 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
