From: Mark Ryden <markryde-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: Rami Rosen <roszenrami-Re5JQEeQqe8AvxtiuMwx3w@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: Tue, 7 Apr 2009 09:10:15 +0300 [thread overview]
Message-ID: <dac45060904062310o3861d05kf1ef24450cd70011@mail.gmail.com> (raw)
In-Reply-To: <1238932997.3782.6.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
Hi,
There is a lot of interest in Linux Wireless around the world. I
believe that many who cannot attend (like me), will be happy if videos
and slides of the presentations will be available afterwards. (as was
done in other Fedora FUDCon conferences in the past).
Regards,
Mark
On Sun, Apr 5, 2009 at 3:03 PM, Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:
> On Sun, 2009-04-05 at 13:52 +0300, Rami Rosen wrote:
>
>> I believe that 802.11n implementation and design in the Linux Wireless stack
>> can be of interest/good to include (also 802.11n Linux future directions ).
>
> I'll be there unless something weird happens -- anything mac80211
> related and especially aggregation (since I rewrote it) I can cover.
>
> johannes
>
--
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
next prev parent reply other threads:[~2009-04-07 6:10 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 [this message]
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
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=dac45060904062310o3861d05kf1ef24450cd70011@mail.gmail.com \
--to=markryde-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@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 \
--cc=roszenrami-Re5JQEeQqe8AvxtiuMwx3w@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).