All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chuck Crisler" <ccrisler@vgocom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: intermittent eap authentication failure
Date: Tue, 18 Jan 2011 10:15:51 -0500	[thread overview]
Message-ID: <14F677785D6A4D4AB3E447B87B4C684F@ChuckPC> (raw)
In-Reply-To: <1295362622.3563.23.camel@jlt3.sipsolutions.net>

Yes, I am advocating for compat-wireless. But have repeated lost a political 
battle over that one. :-(

----- Original Message ----- 
From: "Johannes Berg" <johannes@sipsolutions.net>
To: "Chuck Crisler" <ccrisler@vgocom.com>
Cc: <linux-wireless@vger.kernel.org>
Sent: Tuesday, January 18, 2011 9:57 AM
Subject: Re: intermittent eap authentication failure


> On Tue, 2011-01-18 at 09:54 -0500, Chuck Crisler wrote:
>> I will have to reply later about why it is associating. I will have to 
>> add a
>> printk to my driver but I currently have 2 tests running and don't want 
>> to
>> stop either.
>> It looks like it might be called by ieee80211_sta_work() in mlme.c 
>> because
>> it might still be in the IEEE80211_STA_MLME_ASSOCIATE state. I will 
>> confirm
>> that.
>
> Did you ever consider using compat-wireless? Frankly, my main memory
> isn't large enough to hold information about old mac80211 behaviour so I
> have to get that information from swap (git tree) and that's really
> slow :-)
>
> johannes
>
> 


  reply	other threads:[~2011-01-18 15:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 18:51 intermittent eap authentication failure Chuck Crisler
2011-01-18 10:52 ` Johannes Berg
2011-01-18 14:33   ` Chuck Crisler
2011-01-18 14:54     ` Chuck Crisler
2011-01-18 14:57       ` Johannes Berg
2011-01-18 15:15         ` Chuck Crisler [this message]
2011-01-18 15:21         ` Chuck Crisler
2011-01-18 15:23           ` Johannes Berg
2011-01-18 15:33             ` Chuck Crisler
2011-01-18 15:39               ` Johannes Berg

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=14F677785D6A4D4AB3E447B87B4C684F@ChuckPC \
    --to=ccrisler@vgocom.com \
    --cc=johannes@sipsolutions.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.