From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 0/6] "runtime" iftype switching
Date: Thu, 26 Aug 2010 07:58:00 -0400 [thread overview]
Message-ID: <20100826115800.GA6733@tuxdriver.com> (raw)
In-Reply-To: <1282807400.3812.6.camel@jlt3.sipsolutions.net>
On Thu, Aug 26, 2010 at 09:23:20AM +0200, Johannes Berg wrote:
> On Wed, 2010-08-25 at 17:10 -0400, John W. Linville wrote:
> > On Wed, Aug 25, 2010 at 10:56:19PM +0200, Johannes Berg wrote:
> > > Here's some code to allow runtime (while the
> > > interface is UP) interface type switching,
> > > so far only for STA, IBSS and AP because the
> > > others seem a bit trickier and harder to
> > > verify.
>
> > What is driving this?
>
> Mostly the fact that it's awkward to set the interface down every time,
> because for example every time you do that some IPv6 configuration gets
> lost.
>
> Also, "because I can" :)
Fair enough... :-)
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-08-26 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 20:56 [RFC 0/6] "runtime" iftype switching Johannes Berg
2010-08-25 20:56 ` [RFC 1/6] mac80211: clean up ifdown/cleanup paths Johannes Berg
2010-08-25 20:56 ` [RFC 2/6] mac80211: switch to ieee80211_sdata_running Johannes Berg
2010-08-25 20:56 ` [RFC 3/6] mac80211: simplify zero address checks Johannes Berg
2010-08-25 20:56 ` [RFC 4/6] mac80211: split out concurrent vif checks Johannes Berg
2010-08-25 20:56 ` [RFC 5/6] mac80211: support runtime interface type changes Johannes Berg
2010-08-26 14:22 ` [RFC 5/6 v2] " Johannes Berg
2010-08-25 20:56 ` [RFC 6/6] mac80211_hwsim: support runtime iftype changes Johannes Berg
2010-08-25 21:10 ` [RFC 0/6] "runtime" iftype switching John W. Linville
2010-08-26 7:23 ` Johannes Berg
2010-08-26 11:58 ` John W. Linville [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=20100826115800.GA6733@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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).