From: Johannes Berg <johannes@sipsolutions.net>
To: Andrey Yurovsky <andrey@cozybit.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] cfg80211: allow adding/deleting stations on mesh
Date: Tue, 16 Jun 2009 20:56:53 +0200 [thread overview]
Message-ID: <1245178613.21287.45.camel@johannes.local> (raw)
In-Reply-To: <45e8e6c40906161155i1e5dc5bag114dea7a8c6caa66@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
On Tue, 2009-06-16 at 11:55 -0700, Andrey Yurovsky wrote:
> > Ok, fair enough. There are a lot of quirks in the mesh API, one of these
> > days I'd like to make it less like wext and have you join/leave like the
> > ibss commands instead of setting each parameter one by one...
>
> Thanks. We'd like to hear about any quirks/issues as we have some
> bandwidth to work on mesh again and we would like to address the
> configuration/API issues.
Well mostly it's the thing with configuration parameters affecting the
interface "on the fly". But I'm not familiar enough with all of the
parameters to actually know which ones _can_ change on the fly, and
which ones change and thereby make you part of a different mesh.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-06-16 18:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 18:31 [PATCH] cfg80211: allow adding/deleting stations on mesh Andrey Yurovsky
2009-06-16 18:35 ` Johannes Berg
2009-06-16 18:42 ` Andrey Yurovsky
2009-06-16 18:45 ` Johannes Berg
2009-06-16 18:55 ` Andrey Yurovsky
2009-06-16 18:56 ` Johannes Berg [this message]
2009-06-16 19:32 ` Javier Cardona
2009-06-16 19:37 ` Johannes Berg
2009-06-16 19:51 ` Javier Cardona
2009-06-16 19:59 ` 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=1245178613.21287.45.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=andrey@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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