netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helmut Schaa <helmut.schaa-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: Kalle Valo <kalle.valo-X3B1VOXEql0@public.gmane.org>,
	"John W. Linville"
	<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Linux wireless mini-summit -- Berlin, June 2009
Date: Fri, 8 May 2009 20:09:18 +0200	[thread overview]
Message-ID: <200905082009.18697.helmut.schaa@gmail.com> (raw)
In-Reply-To: <1241802874.4495.25.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>

Am Freitag, 8. Mai 2009 schrieb Johannes Berg:
> 
> > > Feel free to edit and add suggestions
> > 
> > What about proper roaming support? I think it will be the thing we are
> > lacking after power save is finished. There was talk about having GSoC
> > project, what happened to it?
> 
> That project was not accepted - and we even got three.
> 
> > I'm interested about roaming, but I don't how much time if any I can
> > find for implementing it. But I could make a summary of all
> > discussions we have had here during the last year and maybe try to
> > start some discussion at the summit. What others think?
> 
> Sounds useful. Helmut will have input too I guess, and he'll be there.

Yep, a roaming discussion would be great.

Helmut
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2009-05-08 18:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 18:27 Linux wireless mini-summit -- Berlin, June 2009 John W. Linville
     [not found] ` <20090403182724.GA7364-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-04-05 10:52   ` Rami Rosen
     [not found]     ` <b25312890904050352n391f4707mfafca74aef8bca06-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-05 12:03       ` Johannes Berg
     [not found]         ` <1238932997.3782.6.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-04-07  6:10           ` Mark Ryden
2009-06-03 12:35   ` Nick Kossifidis
     [not found]     ` <40f31dec0906030535k3af1f6e7u68c82a4f984e7029-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-03 12:39       ` John W. Linville
2009-06-24 10:19     ` Nick Kossifidis
2009-05-08  9:18 ` Johannes Berg
2009-05-08 16:56   ` Kalle Valo
     [not found]     ` <da94abde0905080956g3c6f49f3ta38412d886cfb2ec-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-08 17:14       ` Johannes Berg
     [not found]         ` <1241802874.4495.25.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-05-08 18:09           ` Helmut Schaa [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=200905082009.18697.helmut.schaa@gmail.com \
    --to=helmut.schaa-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
    --cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
    --cc=kalle.valo-X3B1VOXEql0@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).