From: me@bobcopeland.com
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH] ath5k: eliminate warning unintialized variable warning
Date: Mon, 30 Aug 2010 14:42:16 -0400 [thread overview]
Message-ID: <20100830184216.GA12630@hash.localnet> (raw)
In-Reply-To: <1283192516-3324-1-git-send-email-linville@tuxdriver.com>
On Mon, Aug 30, 2010 at 02:21:56PM -0400, John W. Linville wrote:
> ath5k/base.c:1317: warning: ‘ret’ may be used uninitialized in this function
>
> Reported-by: Johannes Berg <johannes@sipsolutions.net>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Thanks,
Acked-by: Bob Copeland <me@bobcopeland.com>
The first one was cc: stable, do we need to do that too or just
give them a rolled up patch?
--
Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2010-08-30 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 18:11 [PATCH] ath5k: eliminate warning unintialized variable warning John W. Linville
2010-08-30 18:19 ` y
2010-08-30 18:21 ` John W. Linville
2010-08-30 18:42 ` me [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=20100830184216.GA12630@hash.localnet \
--to=me@bobcopeland.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).