From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Linux wireless mini-summit -- Berlin, June 2009
Date: Mon, 4 May 2009 07:53:42 -0700 [thread overview]
Message-ID: <20090504075342.5fd770fd@nehalam> (raw)
In-Reply-To: <20090504121221.GA31147@tuxdriver.com>
On Mon, 4 May 2009 08:12:21 -0400
"John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org> w=
rote:
> On Sun, May 03, 2009 at 11:43:38AM +0300, Kalle Valo wrote:
> > On Tue, Apr 7, 2009 at 11:39 PM, Johannes Berg
> > <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:
> > > Hi,
> >=20
> > Hello,
> >=20
> > >> Also, please consider making some sort of prepared presentation.
> > >> Especially welcome would be topics that are accessible to those
> > >> outside of the core wireless developer group, such as current
> > >> projects on enhancing IBSS support, extended power savings, or a=
ny
> > >> other user-visible topic. =C2=A0I'll be happy to take such propo=
sals in
> > >> private email or you can post them as part of this thread.
> > >
> > > Since I've just booked my train (will arrive 1:30pm or so on the =
25th,
> > > leave Sunday [28th] late afternoon), here are some things I could
> > > possibly talk about:
> > >
> > > =C2=A0* status of moving to nl80211/cfg80211 -- overview over new=
cfg80211
> > > =C2=A0 operations, maybe with Jouni?
> > > =C2=A0* power saving if Kalle can't make it
> >=20
> > I can now confirm that I'm joining the summit as well \o/
> >=20
> > I will arrive to Berlin on Thursday before noon and will leave on
> > Sunday evening.
> >=20
> > Kalle
>=20
> Excellent news! Anyone else?
>=20
> John
I am going to be in France during that period. I might make it,=20
but it requires convincing my spouse that Berlin is worth visting.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-05-04 14:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 18:27 Linux wireless mini-summit -- Berlin, June 2009 John W. Linville
2009-04-05 5:06 ` Kalle Valo
2009-04-05 10:52 ` Rami Rosen
2009-04-05 12:03 ` Johannes Berg
2009-04-07 6:10 ` Mark Ryden
2009-04-07 15:28 ` Alina Friedrichsen
2009-04-07 20:39 ` Johannes Berg
2009-05-03 8:43 ` Kalle Valo
2009-05-04 12:12 ` John W. Linville
2009-05-04 14:53 ` Stephen Hemminger [this message]
2009-05-04 15:07 ` Holger Schurig
2009-05-04 15:55 ` Marcel Holtmann
2009-05-04 17:02 ` Samuel Ortiz
2009-05-08 9:01 ` Helmut Schaa
2009-05-09 7:18 ` Henning Rogge
2009-05-09 14:21 ` Nick Kossifidis
2009-05-09 14:36 ` Henning Rogge
2009-05-29 10:54 ` Luis Correia
2009-05-08 9:18 ` Johannes Berg
2009-05-08 16:56 ` Kalle Valo
2009-05-08 17:14 ` Johannes Berg
2009-05-08 18:09 ` Helmut Schaa
2009-06-03 12:35 ` Nick Kossifidis
2009-06-03 12:39 ` John W. Linville
2009-06-24 10:19 ` Nick Kossifidis
-- strict thread matches above, loose matches on Subject: below --
2009-06-24 11:47 Kevin Wilson
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=20090504075342.5fd770fd@nehalam \
--to=shemminger@linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@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).