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 0/2 v3] cfg80211: mac80211: 802.11p OCB mode support
Date: Tue, 04 Nov 2014 10:25:48 +0100 [thread overview]
Message-ID: <1415093148.2064.5.camel@sipsolutions.net> (raw)
In-Reply-To: <1415007199-31506-1-git-send-email-rostislav.lisovy@fel.cvut.cz> (sfid-20141103_103325_972796_F4E0AE3F)
On Mon, 2014-11-03 at 10:33 +0100, Rostislav Lisovy wrote:
> The IEEE 802.11p amendment (already part of IEEE 802.11-2012)
> specifies usage of 5 and 10 MHz wide channels in 5.9GHz band for
> vehicular environment. All the 802.11p compliant devices should
> be set to the newly added operation mode -- OCB (Outside the
> Context of a BSS). No authentication/association is necessary to
> communicate. The only parameter to be configured is the channel
> (central frequency and bandwidth) to communicate on. The channel
> has to be known a priori. It is set during the 'ocb join'
> operation (sent via netlink message from user-space).
>
> This patchset adds the OCB mode, OCB join and leave handling
> (nl80211, cfg80211, mac80211), 802.11p EDCA parameters
> modification, RX and TX path (for unicast/broadcast messages).
Applied, thanks for all the changes.
johannes
next prev parent reply other threads:[~2014-11-04 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 9:33 [PATCH 0/2 v3] cfg80211: mac80211: 802.11p OCB mode support Rostislav Lisovy
2014-11-03 9:33 ` [PATCH 1/2] cfg80211: mac80211: 802.11p OCB mode handling Rostislav Lisovy
2014-11-03 9:33 ` [PATCH 2/2] mac80211: 802.11p OCB mode support Rostislav Lisovy
2014-11-04 9:25 ` Johannes Berg [this message]
2014-11-04 12:58 ` [PATCH 0/2 v3] cfg80211: " Rostislav Lisovy
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=1415093148.2064.5.camel@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 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.