From: Bob Copeland <me@bobcopeland.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: mcgrof@gmail.com, jirislaby@gmail.com,
linux-wireless@vger.kernel.org, ath5k-devel@lists.ath5k.org
Subject: Re: [PATCH] ath5k: Fix loop variable initializations
Date: Mon, 12 May 2008 20:17:26 -0400 [thread overview]
Message-ID: <20080513001726.GA23128@hash.localnet> (raw)
In-Reply-To: <40f31dec0805121618j4a2f8bedw78e2ce36d8158649@mail.gmail.com>
On Tue, May 13, 2008 at 02:18:48AM +0300, Nick Kossifidis wrote:
> Why not doing a simple
> rxs.flag = 0 ;
> or a check of flags set by mac80211 at the start of the loop ?
Yeah that's a better idea. I'll respin the patch with this and the
other suggestion.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2008-05-13 0:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 14:30 [PATCH] ath5k: Fix loop variable initializations Bob Copeland
2008-05-12 20:27 ` Helge Deller
2008-05-12 23:18 ` Nick Kossifidis
2008-05-13 0:17 ` Bob Copeland [this message]
2008-05-13 1:16 ` Bob Copeland
2008-05-12 23:25 ` Nick Kossifidis
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=20080513001726.GA23128@hash.localnet \
--to=me@bobcopeland.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=mickflemm@gmail.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