From: Pavel Roskin <proski@gnu.org>
To: Felix Fietkau <nbd@openwrt.org>
Cc: Richard Zidlicky <rz@linux-m68k.org>, linux-wireless@vger.kernel.org
Subject: Re: rc80211_minstrel.c:70 WARNING with 2.6.34-rc4
Date: Thu, 22 Apr 2010 17:38:41 -0400 [thread overview]
Message-ID: <1271972321.12589.2.camel@mj> (raw)
In-Reply-To: <4BCC9A27.9000104@openwrt.org>
On Mon, 2010-04-19 at 20:00 +0200, Felix Fietkau wrote:
> > can that happen when both ends are configured to a fixed rate of 11M?
> No idea. I've never used fixed-rate. I guess it could, if it uses 11M
> for communicating with a peer that it for some reason did not enable
> this rate for.
I think if there is a legitimate condition when it can happen, we should
not be using WARN_ON.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-04-22 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 8:56 rc80211_minstrel.c:70 WARNING with 2.6.34-rc4 Richard Zidlicky
2010-04-19 16:34 ` Pavel Roskin
2010-04-19 17:41 ` Richard Zidlicky
2010-04-19 17:41 ` Felix Fietkau
2010-04-19 17:55 ` Richard Zidlicky
2010-04-19 18:00 ` Felix Fietkau
2010-04-22 21:38 ` Pavel Roskin [this message]
2010-04-22 22:15 ` Richard Zidlicky
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=1271972321.12589.2.camel@mj \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=rz@linux-m68k.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).