From: "John W. Linville" <linville@tuxdriver.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] doesn't look like we made a track at linux plumbers
Date: Mon, 13 Jun 2011 16:32:04 -0400 [thread overview]
Message-ID: <20110613203203.GB2495@tuxdriver.com> (raw)
In-Reply-To: <BANLkTimSurx5rd+Um-s3y9btL7tbbHm8wg@mail.gmail.com>
On Mon, Jun 13, 2011 at 09:08:13AM -0600, Dave Taht wrote:
> :(
This is news to me (and I'm on the program committee) -- where did
you hear this?
> But:
>
> http://linuxwireless.org/en/developers/Summits/Vancouver-2011
>
> In mid-august, looks more apt, followed by linuxcon.
>
> We are also getting close to a point where it would be fun and
> informative to be
> testing debloated routers at scale, too.
>
> Can we still get in this conference?
I have been approved for a bufferbloat speaking slot at LinuxCon.
John
--
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:[~2011-06-13 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 15:08 Dave Taht
2011-06-13 20:32 ` John W. Linville [this message]
2011-06-13 21:19 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110613203203.GB2495@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@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