From: Johannes Berg <johannes@sipsolutions.net>
To: Hin-Tak Leung <hintak.leung@gmail.com>
Cc: Albert Herranz <albert_herranz@yahoo.es>,
Holger Schurig <hs4233@mail.mn-solutions.de>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: Problems with "cfg80211: fix SME connect" commit
Date: Mon, 28 Sep 2009 16:41:44 +0200 [thread overview]
Message-ID: <1254148904.3151.4.camel@johannes.local> (raw)
In-Reply-To: <3ace41890909261657s53b38a2fl7939740fc53dd594@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On Sun, 2009-09-27 at 00:57 +0100, Hin-Tak Leung wrote:
> I suppose (together with some of the newly added printk you mentioned
> could be removed in the final version) the dmesg messages are somewhat
> confusing, because as a user, I would rather have a deauth message
> that's actually associated with a user action (e.g. if I switch AP or
> rfkill). Is it possible to distinguish situation where a user action
> is involved versus one that isn't? or is the distinction between any
> consequence of 'user-action' vs wpa_supplicant doing-it-on-its-own too
> much buried down in the layers?
Yeah, it'd be nice to avoid that completely. Or even just avoid telling
the driver, maybe with some delay akin iwcommit. Alas, I haven't looked
at it yet and right now it seems to just be a message (and possibly a
deauth frame)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-09-28 14:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 18:03 Problems with "cfg80211: fix SME connect" commit Albert Herranz
2009-09-21 6:45 ` Holger Schurig
2009-09-21 16:11 ` Albert Herranz
2009-09-24 8:05 ` Johannes Berg
2009-09-24 19:13 ` Hin-Tak Leung
2009-09-25 6:22 ` Johannes Berg
2009-09-25 15:54 ` Hin-Tak Leung
2009-09-26 11:39 ` Johannes Berg
2009-09-26 23:57 ` Hin-Tak Leung
2009-09-28 14:41 ` Johannes Berg [this message]
2009-09-30 21:17 ` Hin-Tak Leung
2009-09-30 21:20 ` Johannes Berg
2009-09-28 18:04 ` Albert Herranz
2009-09-28 18:55 ` Johannes Berg
2009-09-28 19:22 ` Hin-Tak Leung
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=1254148904.3151.4.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=albert_herranz@yahoo.es \
--cc=hintak.leung@gmail.com \
--cc=hs4233@mail.mn-solutions.de \
--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).