From: Pavel Roskin <proski@gnu.org>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@atheros.com,
linville@tuxdriver.com
Subject: Re: ath: Fix uninitialized variable warnings [v2]
Date: Tue, 06 Jul 2010 12:35:58 -0400 [thread overview]
Message-ID: <1278434158.20061.1.camel@mj> (raw)
In-Reply-To: <4C331BB9.5010005@redhat.com>
On Tue, 2010-07-06 at 08:04 -0400, Prarit Bhargava wrote:
> New patch with updated description.
Your patch doesn't apply anymore.
> Fix 'make CONFIG_DEBUG_SECTION_MISMATCH=y' warning:
I tried to reproduce the warning, but could not. I guess my gcc is old
(4.4.1) or you used more options that enable warnings.
> Pavel pointed out that tMinCalPower or pMinCalPower isn't used anywhere, so
> the simplest way to fix these warnings is to get rid of the code.
That alone is the best reason. I'll resend the updated patch.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2010-07-06 16: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
2010-07-06 12:04 ` Prarit Bhargava
2010-07-06 16:35 ` Pavel Roskin [this message]
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=1278434158.20061.1.camel@mj \
--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).