From: Sascha Silbe <sascha-ml-reply-to-2011-2@silbe.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
devel <devel@lists.laptop.org>, Dan Williams <dcbw@redhat.com>,
John@xo15-sascha.sascha.silbe.org,
W.Linville@xo15-sascha.sascha.silbe.org, <linville@tuxdriver.com>,
libertas-dev <libertas-dev@lists.infradead.org>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add libertas_disablemesh module parameter to disable mesh interface
Date: Fri, 13 May 2011 15:26:24 +0200 [thread overview]
Message-ID: <1305292756-sup-4842@xo15-sascha.sascha.silbe.org> (raw)
In-Reply-To: <20110511100030.cad34893.rdunlap@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
Excerpts from Randy Dunlap's message of Wed May 11 19:00:30 +0200 2011:
> On Wed, 11 May 2011 14:52:34 +0200 Sascha Silbe wrote:
>
> > This allows individual users and deployments to disable mesh support at
> > runtime, i.e. without having to build and maintain a custom kernel.
>
> I guess a user could want to do this on a per-driver basis, but ISTM that
> it would be better to be something like a sysctl that applies to all (wireless)
> drivers.
AFAIK libertas is the only driver with a mesh implementation based on an
outdated 802.11s draft. To clarify, we could rename the parameter to
lbs_disable_olpcmesh (or just disable_olpcmesh).
Disabling 802.11s (latest draft) based mesh support is a separate
matter.
Sascha
--
http://sascha.silbe.org/
http://www.infra-silbe.de/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Sascha Silbe <silbe@activitycentral.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
devel <devel@lists.laptop.org>, Dan Williams <dcbw@redhat.com>,
John@xo15-sascha.sascha.silbe.org,
W.Linville@xo15-sascha.sascha.silbe.org, <linville@tuxdriver.com>,
libertas-dev <libertas-dev@lists.infradead.org>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add libertas_disablemesh module parameter to disable mesh interface
Date: Fri, 13 May 2011 15:26:24 +0200 [thread overview]
Message-ID: <1305292756-sup-4842@xo15-sascha.sascha.silbe.org> (raw)
In-Reply-To: <20110511100030.cad34893.rdunlap@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
Excerpts from Randy Dunlap's message of Wed May 11 19:00:30 +0200 2011:
> On Wed, 11 May 2011 14:52:34 +0200 Sascha Silbe wrote:
>
> > This allows individual users and deployments to disable mesh support at
> > runtime, i.e. without having to build and maintain a custom kernel.
>
> I guess a user could want to do this on a per-driver basis, but ISTM that
> it would be better to be something like a sysctl that applies to all (wireless)
> drivers.
AFAIK libertas is the only driver with a mesh implementation based on an
outdated 802.11s draft. To clarify, we could rename the parameter to
lbs_disable_olpcmesh (or just disable_olpcmesh).
Disabling 802.11s (latest draft) based mesh support is a separate
matter.
Sascha
--
http://sascha.silbe.org/
http://www.infra-silbe.de/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Sascha Silbe <sascha-ml-reply-to-2011-2-OgEpK5h/+1LYtjvyW6yDsg@public.gmane.org>
To: Randy Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
Cc: linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
devel <devel-oU9gvf+ajcRuEWckB3OYtg@public.gmane.org>,
Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
John-i2JScjCrrBUtjPN9IyLgGT5Lv7v+73c5YPYVAmT7z5s@public.gmane.org,
W.Linville-i2JScjCrrBUtjPN9IyLgGT5Lv7v+73c5YPYVAmT7z5s@public.gmane.org,
<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
libertas-dev
<libertas-dev-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] Add libertas_disablemesh module parameter to disable mesh interface
Date: Fri, 13 May 2011 15:26:24 +0200 [thread overview]
Message-ID: <1305292756-sup-4842@xo15-sascha.sascha.silbe.org> (raw)
In-Reply-To: <20110511100030.cad34893.rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
Excerpts from Randy Dunlap's message of Wed May 11 19:00:30 +0200 2011:
> On Wed, 11 May 2011 14:52:34 +0200 Sascha Silbe wrote:
>
> > This allows individual users and deployments to disable mesh support at
> > runtime, i.e. without having to build and maintain a custom kernel.
>
> I guess a user could want to do this on a per-driver basis, but ISTM that
> it would be better to be something like a sysctl that applies to all (wireless)
> drivers.
AFAIK libertas is the only driver with a mesh implementation based on an
outdated 802.11s draft. To clarify, we could rename the parameter to
lbs_disable_olpcmesh (or just disable_olpcmesh).
Disabling 802.11s (latest draft) based mesh support is a separate
matter.
Sascha
--
http://sascha.silbe.org/
http://www.infra-silbe.de/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2011-05-13 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 12:52 [PATCH] Add libertas_disablemesh module parameter to disable mesh interface Sascha Silbe
2011-05-11 12:52 ` Sascha Silbe
2011-05-11 17:00 ` Randy Dunlap
2011-05-13 13:26 ` Sascha Silbe [this message]
2011-05-13 13:26 ` Sascha Silbe
2011-05-13 13:26 ` Sascha Silbe
2011-05-12 3:11 ` Dan Williams
2011-05-13 13:16 ` Sascha Silbe
2011-05-13 13:16 ` Sascha Silbe
2011-05-13 13:16 ` Sascha Silbe
2011-05-19 17:16 ` Dan Williams
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=1305292756-sup-4842@xo15-sascha.sascha.silbe.org \
--to=sascha-ml-reply-to-2011-2@silbe.org \
--cc=John@xo15-sascha.sascha.silbe.org \
--cc=W.Linville@xo15-sascha.sascha.silbe.org \
--cc=dcbw@redhat.com \
--cc=devel@lists.laptop.org \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.