From: Dan Williams <dcbw@redhat.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: "Stefanik Gábor" <netrolller.3d@gmail.com>,
"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 -- Ottawa -- July 22, 2008
Date: Tue, 15 Jul 2008 13:16:31 -0400 [thread overview]
Message-ID: <1216142191.6039.113.camel@localhost.localdomain> (raw)
In-Reply-To: <200807101815.27204.mb@bu3sch.de>
On Thu, 2008-07-10 at 18:15 +0200, Michael Buesch wrote:
> On Thursday 10 July 2008 18:12:32 Stefanik G=C3=A1bor wrote:
> > Some other topics which might be of interest/good to include:
> > - New chipsets needing drivers (SiS 16x, Marvell, etc.)
>=20
> I have no idea what to discuss about non-existing drivers, really.
> Something like: "Do we need that driver? Everyone votes YES and is ha=
ppy"?
Maybe during the week we could organize some hackfests to work on the
Marvell/SiS/etc mac80211 drivers? Everyone bring their favorite
non-working Marvell 88w83xx card and we make mrv8k our bitch or
something like that.
Dan
> > - Radiotap enhancements
>=20
> What radiotap enhancements specifically? If it's just a field or a bi=
t
> to add, just mail the radiotap people. I think there's no need to dis=
cuss that
> (except for with the radiotap people on their mailinglist).
>=20
> > - Userspace MLME: Plans and status
>=20
> Already on the list.
>=20
--
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:[~2008-07-15 17:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 19:09 Linux Wireless Mini-Summit -- Ottawa -- July 22, 2008 John W. Linville
2008-07-10 0:13 ` Tomas Winkler
2008-07-10 6:52 ` Ron Rindjunsky
2008-07-10 14:30 ` Kalle Valo
2008-07-11 1:41 ` Jouni Malinen
2008-07-11 4:46 ` Kalle Valo
2008-07-10 6:41 ` Mark Ryden
2008-07-10 7:21 ` Holger Schurig
2008-07-10 7:23 ` Johannes Berg
2008-07-10 10:22 ` Johannes Berg
2008-07-10 10:50 ` Tomas Winkler
2008-07-10 14:31 ` Johannes Berg
2008-07-10 15:15 ` Tomas Winkler
2008-07-10 15:52 ` Inaky Perez-Gonzalez
2008-07-10 16:12 ` Stefanik Gábor
2008-07-10 16:15 ` Michael Buesch
2008-07-15 17:16 ` Dan Williams [this message]
2008-07-15 17:31 ` Nicolas Pitre
2008-07-15 17:58 ` Dan Williams
2008-07-15 18:02 ` Dan Williams
2008-07-15 18:14 ` Nicolas Pitre
2008-07-15 18:38 ` Dan Williams
2008-07-21 14:23 ` Dan Williams
2008-07-21 16:46 ` Nicolas Pitre
2008-07-15 18:20 ` Kalle Valo
2008-07-14 15:05 ` Guy Cohen
2008-07-15 17:42 ` John W. Linville
2008-07-15 18:15 ` Dan Williams
2008-07-16 8:24 ` Johannes Berg
2008-07-16 16:27 ` Dan Williams
2008-07-14 15:43 ` Guy Cohen
2008-07-15 18:26 ` REVISED AGENDA -- " John W. Linville
2008-07-16 8:40 ` Johannes Berg
2008-07-16 11:29 ` Tomas Winkler
2008-07-16 18:48 ` 2nd " John W. Linville
2008-07-16 19:58 ` John W. Linville
2008-07-17 10:05 ` Luis R. Rodriguez
2008-07-17 10:16 ` Luis R. Rodriguez
2008-07-18 23:23 ` 3rd " John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2008-07-10 7:41 Joerg Pommnitz
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=1216142191.6039.113.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
/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