From: Johannes Berg <johannes@sipsolutions.net>
To: Rostislav Lisovy <lisovy@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Sojka <sojkam1@fel.cvut.cz>,
s.sander@nordsys.de, jan-niklas.meier@volkswagen.de,
burak.simsek@volkswagen.de,
Emmanuel Thierry <emmanuel.thierry@yogoko.fr>,
laszlo.virag@commsignia.com,
Rostislav Lisovy <rostislav.lisovy@fel.cvut.cz>
Subject: Re: [PATCH 1/4] mac80211: OCB mode + join and leave handling
Date: Mon, 20 Oct 2014 11:41:45 +0200 [thread overview]
Message-ID: <1413798105.10246.9.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1413480005.16330.15.camel@umadbro> (sfid-20141016_192008_718892_BA5E5317)
On Thu, 2014-10-16 at 19:20 +0200, Rostislav Lisovy wrote:
> Now I realized it is not that easy (and I confused "interface running"
> and being "connected to the network"). There seems not to be a solid
> indication that we are no longer "connected" to the network.
Oops, ignore my previous reply.
> I think a field
> enum {
> IEEE80211_OCB_STOPPED,
> IEEE80211_OCB_JOINED,
> } state;
> in struct ieee80211_if_ocb seems to be appropriate.
Yes, that seems doable. Maybe just a "bool joined" would work just as
well, but it won't make a difference in the result - whichever you
prefer.
johannes
next prev parent reply other threads:[~2014-10-20 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 14:30 [PATCH 0/4] 802.11p OCB mode Rostislav Lisovy
2014-09-11 14:30 ` [PATCH 1/4] mac80211: OCB mode + join and leave handling Rostislav Lisovy
2014-10-09 8:23 ` Johannes Berg
2014-10-16 16:33 ` Rostislav Lisovy
2014-10-16 17:20 ` Rostislav Lisovy
2014-10-20 9:41 ` Johannes Berg [this message]
2014-10-20 9:40 ` Johannes Berg
2014-09-11 14:30 ` [PATCH 2/4] mac80211: Use different EDCA config for OCB Rostislav Lisovy
2014-09-11 14:30 ` [PATCH 3/4] cfg80211: Join and Leave handling for OCB mode Rostislav Lisovy
2014-10-09 8:26 ` Johannes Berg
2014-09-11 14:30 ` [PATCH 4/4] nl80211: " Rostislav Lisovy
2014-10-09 8:31 ` 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=1413798105.10246.9.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=burak.simsek@volkswagen.de \
--cc=emmanuel.thierry@yogoko.fr \
--cc=jan-niklas.meier@volkswagen.de \
--cc=laszlo.virag@commsignia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lisovy@gmail.com \
--cc=rostislav.lisovy@fel.cvut.cz \
--cc=s.sander@nordsys.de \
--cc=sojkam1@fel.cvut.cz \
/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