linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Rostislav Lisovy <lisovy@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	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,
	Rostislav Lisovy <rostislav.lisovy@fel.cvut.cz>
Subject: Re: [PATCH 0/2 v3] cfg80211: The very first steps to support 5/10MHz channels in 5.9Ghz band
Date: Fri, 25 Apr 2014 17:40:33 +0200	[thread overview]
Message-ID: <1398440433.4152.22.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1397565476-4348-1-git-send-email-rostislav.lisovy@fel.cvut.cz> (sfid-20140415_143803_281449_E72A76A1)

On Tue, 2014-04-15 at 14:37 +0200, Rostislav Lisovy wrote:
> The IEEE 802.11p amendment specifies usage of 5 and 10 MHz wide
> channels in 5.9GHz band for vehicular environment. This patch-set
> adds new channel attributes holding the information about the
> prohibited bandwidths. This is meant to be used mainly with
> channels in 5.9GHz band in future implementation of 802.11p.

Both applied.

johannes


      parent reply	other threads:[~2014-04-25 15:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 12:37 [PATCH 0/2 v3] cfg80211: The very first steps to support 5/10MHz channels in 5.9Ghz band Rostislav Lisovy
2014-04-15 12:37 ` [PATCH 1/2] cfg80211: Add attributes describing prohibited channel bandwidth Rostislav Lisovy
2014-04-15 12:37 ` [PATCH 2/2] cfg80211: Use 5MHz bandwidth by default when checking usable channels Rostislav Lisovy
2014-06-22 11:41   ` Felix Fietkau
2014-06-23  9:08     ` Johannes Berg
2014-06-23 10:04       ` Felix Fietkau
2014-06-23 10:05         ` Johannes Berg
2014-06-23 14:38           ` Rostislav Lisovy
2014-06-23 14:46             ` Felix Fietkau
2014-06-23 14:58               ` Rostislav Lisovy
2014-04-25 15:40 ` Johannes Berg [this message]

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=1398440433.4152.22.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=jan-niklas.meier@volkswagen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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;
as well as URLs for NNTP newsgroup(s).