netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Linux wireless mini-summit -- Berlin, June 2009
Date: Fri, 8 May 2009 19:56:38 +0300	[thread overview]
Message-ID: <da94abde0905080956g3c6f49f3ta38412d886cfb2ec@mail.gmail.com> (raw)
In-Reply-To: <1241774338.1567.36.camel@johannes.local>

On Fri, May 8, 2009 at 12:18 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
>
>> So, here I open the floor for discussion of agenda items for our
>> wireless meeting/hackfest.  What do we think is important to discuss
>> face-to-face this year?  What isn't getting done?  What is getting
>> done wrong?  What do we need that we didn't realize last year?
>
> I've tried to capture the discussion from here on the wiki:
>
> http://wireless.kernel.org/en/developers/Summits/Berlin-2009

Good idea.

> 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?

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?

> or put yourself into "confirmed
> attendees" (do we want that? it seemed we should say who will be there)

It's nice to know in advance who will be there. So yes, at least I
want such a list :)

Kalle

  reply	other threads:[~2009-05-08 16:56 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 [this message]
     [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

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=da94abde0905080956g3c6f49f3ta38412d886cfb2ec@mail.gmail.com \
    --to=kalle.valo@iki.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@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).