From: Prarit Bhargava <prarit@redhat.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@atheros.com,
linville@tuxdriver.com
Subject: Re: ath: Fix uninitialized variable warnings [v2]
Date: Sat, 03 Jul 2010 15:27:35 -0400 [thread overview]
Message-ID: <4C2F8F27.50405@redhat.com> (raw)
In-Reply-To: <1278165872.6710.1.camel@mj>
On 07/03/2010 10:04 AM, Pavel Roskin wrote:
> On Thu, 2010-07-01 at 12:09 -0400, Prarit Bhargava wrote:
>
>> Fix 'make CONFIG_DEBUG_SECTION_MISMATCH=y' warning:
>>
> I don't think the warnings you are fixing have anything to do with
> CONFIG_DEBUG_SECTION_MISMATCH.
>
Actually, Pavel -- they do. I've already emailed a question to some of
the gcc developers to see if they can explain to me why *I only see
these warnings if CONFIG_DEBUG_SECTION_MISMATCH is enabled*.
I agree, however, that it shouldn't make a difference and that it may
show a bug in gcc or somewhere in our makefiles.
>> drivers/net/wireless/mwl8k.c: In function 'mwl8k_bss_info_changed_sta':
>> drivers/net/wireless/mwl8k.c:3404: warning: 'ap_legacy_rates' may be used uninitialized in this function
>>
> The patch doesn't appear to touch mwl8k.c at all.
>
> Please fix the description.
>
>
Will do -- sorry, I cut-and-pasted too much...
P.
next prev parent reply other threads:[~2010-07-03 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 16:09 ath: Fix uninitialized variable warnings [v2] Prarit Bhargava
2010-07-03 14:04 ` Pavel Roskin
2010-07-03 19:27 ` Prarit Bhargava [this message]
2010-07-06 12:04 ` Prarit Bhargava
2010-07-06 16:35 ` Pavel Roskin
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=4C2F8F27.50405@redhat.com \
--to=prarit@redhat.com \
--cc=ath9k-devel@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=proski@gnu.org \
/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).