From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Cc: johannes@sipsolutions.net, marcel@holtmann.org,
Samuel Ortiz <samuel@sortiz.org>,
Gustavo Padovan <gustavo@padovan.org>,
linux-bluetooth@vger.kernel.org, linux-nfc@ml01.01.org
Subject: Re: Linux Wireless Mini-Summit in New Orleans -- 19-20 September (6 weeks from today!)
Date: Thu, 8 Aug 2013 15:04:29 -0400 [thread overview]
Message-ID: <20130808190428.GF30925@tuxdriver.com> (raw)
In-Reply-To: <20130808185410.GD30925@tuxdriver.com>
Sorry, forgot to copy linux-bluetooth and linux-nfc...
On Thu, Aug 08, 2013 at 02:54:11PM -0400, John W. Linville wrote:
> Greetings!
>
> This is a reminder that we will have a Linux Wireless Mini-Summit in
> New Orleans this year on 19-20 September. This will immediately follow
> LinuxCon and will run concurrently with Linux Plumber's Conference.
> This event includes Linux developers for wireless LAN (802.11),
> Bluetooth, and NFC technologies. Both kernel and userland developers
> are welcomed and heartily encouraged to attend!
>
> http://wireless.kernel.org/en/developers/Summits/New-Orleans-2013
>
> The link above is a Wiki. We are using it to collect discussion
> topics and to negotiate agenda/scheduling options for the event.
> Please go there to record your intent to attend the event and to
> propopse topics for discussion.
>
> Please be aware that in order to attend the event above one must
> register for either LinuxCon or for Linux Plumbers Conference.
> Act now, before those events fill-up and close their registrations!
>
> We are allotted one "large" room (up to ~80 people "theater style"), and
> two "small" rooms (up to ~25 people) for this event. Based on history
> and the numbers of contributors, the larger room will primarily be
> for the 802.11 discussions and any "plenary" topics while the smaller
> rooms will be for Bluetooth, NFC, and any "breakout" topics.
>
> So...thoughts? Topics to discuss?
>
> John
> --
> John W. Linville Someday the world will need a hero, and you
> linville@tuxdriver.com might be all we have. Be ready.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-08-08 19:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 18:54 Linux Wireless Mini-Summit in New Orleans -- 19-20 September (6 weeks from today!) John W. Linville
2013-08-08 19:04 ` John W. Linville [this message]
2013-09-05 13:39 ` John W. Linville
2013-09-05 16:04 ` Dan Williams
2013-09-09 19:23 ` Linux Wireless Mini-Summit in New Orleans -- 19-20 September John W. Linville
2013-09-09 20:48 ` [linux-nfc] " Marcel Holtmann
2013-09-10 9:46 ` Samuel Ortiz
2013-09-09 21:50 ` Seth Forshee
2013-09-10 6:28 ` Luca Coelho
2013-09-10 7:59 ` Arend van Spriel
2013-09-12 18:38 ` Daniel Wagner
2013-09-12 18:48 ` John W. Linville
2013-09-12 19:26 ` Dan Williams
2013-09-12 19:31 ` Daniel Wagner
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=20130808190428.GF30925@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=gustavo@padovan.org \
--cc=johannes@sipsolutions.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-nfc@ml01.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=samuel@sortiz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.