From: Pavel Roskin <proski@gnu.org>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
ath9k-devel@atheros.com
Subject: Re: [PATCH]: ath: Fix uninitialized variable warnings
Date: Sat, 19 Jun 2010 13:33:07 -0400 [thread overview]
Message-ID: <1276968787.29943.0.camel@ct> (raw)
In-Reply-To: <4C1AA4AF.8040306@redhat.com>
On Thu, 2010-06-17 at 18:41 -0400, Prarit Bhargava wrote:
...
> New linux-2.6 patch using Pavel's suggestion.
>
>
> Fix "make -j32 CONFIG_DEBUG_SECTION_MISMATCH=y" warning:
>
> 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:301: warning: ‘minPwrT4’ may be used uninitialized in this function
> 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:310: warning: ‘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:677: warning: ‘minPwrT4’ may be used uninitialized in this function
>
> Remove tMinCalPower and the corresponding function arguments as it is not
> used.
>
> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Acked-by: Pavel Roskin <proski@gnu.org>
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-06-19 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100527181052.23905.67123.sendpatchset@prarit.bos.redhat.com>
2010-05-28 17:34 ` [PATCH]: ath: Fix uninitialized variable warnings John W. Linville
2010-05-28 20:44 ` Pavel Roskin
2010-06-17 22:41 ` Prarit Bhargava
2010-06-19 17:33 ` Pavel Roskin [this message]
2010-05-27 18:15 Prarit Bhargava
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=1276968787.29943.0.camel@ct \
--to=proski@gnu.org \
--cc=ath9k-devel@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=prarit@redhat.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).