ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Wireless Networking Workshop
Date: Fri, 6 Jun 2014 15:55:11 -0400	[thread overview]
Message-ID: <20140606195511.GA13595@tuxdriver.com> (raw)

I would like to propose a wireless networking workshop as part of
the Kernel Summit events in Chicago.  We have a wireless networking
miniconf scheduled for LPC.  I see the event I am proposing now as
being more kernel-focused to deal with deeper development issues.

Some potential topics:

	-- framework for handling firmware dumps and debugging

	-- an nl80211 vendor command retrospective

	-- new/rising technologies (WFDS, HotSpot 2.0, etc)

	-- wireless regulatory code (who understands it?)

	-- ??

There were a number of wireless kernel developers on the
auto-nomination list.  Hopefully some of those are already invited
to KS or are planning to attend LCNA?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

                 reply	other threads:[~2014-06-06 20:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140606195511.GA13595@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=ksummit-discuss@lists.linuxfoundation.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