From: Johannes Berg <johannes@sipsolutions.net>
To: greearb@candelatech.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wireless: Remove spurious warning in mlme.c
Date: Wed, 08 Dec 2010 09:11:43 +0100 [thread overview]
Message-ID: <1291795903.3562.5.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1291759599-14698-1-git-send-email-greearb@candelatech.com>
On Tue, 2010-12-07 at 14:06 -0800, greearb@candelatech.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> Seems that we should not be warning if all of the
> authtry_bsses are already NULL.
Do you keep running into the warning? I'd really like to understand how
it happens -- it seems to point to a mac80211 bug.
So don't really like this patch.
johannes
next prev parent reply other threads:[~2010-12-08 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 22:06 [PATCH] wireless: Remove spurious warning in mlme.c greearb
2010-12-07 23:05 ` Gábor Stefanik
2010-12-08 8:11 ` Johannes Berg [this message]
2010-12-08 15:36 ` Ben Greear
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=1291795903.3562.5.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.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).