From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "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: Thu, 10 Jul 2008 18:15:07 +0300 [thread overview]
Message-ID: <1ba2fa240807100815j6bda3c63q4fc4d0c5da826fe3@mail.gmail.com> (raw)
In-Reply-To: <1215700309.3483.21.camel@johannes.berg>
On Thu, Jul 10, 2008 at 5:31 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
>
>> 1500 Future work
>
> Maybe something about testing? Or I'll do a testing brainstorming
> session after dinner.
>
> Obviously, testing at orbit never worked out, but it'd be good to have
> _something_ other than everybody testing their thing locally. Ties in
> with the virtual hardware, maybe?
>
>From the driver perspective it would be loop back phy (tx/rx), The
peer side might be running on virtual HW. Currently it's not easy to
establish automated regression over the air. Good portion of the flows
can be tested this way.
I'm also looking for easier bug reporting for unexperienced users
maybe some uevent/HAL popping to application and emails it out/. Not
sure really how to handle this and not create spams. I'm just
expecting more real 'end users'.
Thanks
Tomas
next prev parent reply other threads:[~2008-07-10 15:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 19:09 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 [this message]
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
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-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 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
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=1ba2fa240807100815j6bda3c63q4fc4d0c5da826fe3@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®