[RFC 0/4] refactor station state management

[Johannes Berg <johannes@sipsolutions.net>]

Here's a first step towards something I talked to some
of you about -- making drivers more aware of station
state.

Because experience tells me that drivers will be written
for the common case, and forget about uncommon sequences,
this first step enforces proper ordering of states, now
a station can move only between these states like this:
 NONE  <--> AUTHENTICATED <--> ASSOCIATED <--> AUTHORIZED

As a consequence, IBSS stations and WDS peers need to
go through ASSOCIATED state (and get ASSOC flag set),
but this doesn't seem to be an issue, in fact it makes
at least one place in the code simpler.

This patchset still has two issues:
 * secure mesh is broken right now I think, its state
   change possibilities are rather confusing
   (need help to fix this, at least explanations)
 * TLDS isn't handled (maybe not an issue?)


My further plan is the following:
 1) figure out the issues above
 2) notify drivers of these state changes
 3) refactor auth/assoc process as described before
  a) don't track multiple authentications
  b) don't try to keep an existing authentication/association
  c) set channel first etc.
 4) remove dummy station code
  a) add regular station entry before auth
  b) notify to AUTH state when auth succeeds
  c) notify to ASSOC state when assoc succeeds

This patchset is but the first step on this journey, at the
end of which we will hopefully find multi-channel support :-)

johannes