From: David Miller <davem@davemloft.net>
To: Matt_Domsch@Dell.com
Cc: netdev@vger.kernel.org
Subject: Re: Linux Plumbers Conference: User-visible Network Issues Mini-Conf
Date: Fri, 17 Sep 2010 15:57:46 -0700 (PDT) [thread overview]
Message-ID: <20100917.155746.171491800.davem@davemloft.net> (raw)
In-Reply-To: <1B9798A3396AB0429545ADFEA207931510536C7C8E@AUSX7MCPS302.AMER.DELL.COM>
From: <Matt_Domsch@Dell.com>
Date: Fri, 17 Sep 2010 14:12:29 -0500
> At the Linux Plumbers Conference [1] November 3-5, 2010 in
> Cambridge, MA, we have a half-day mini-conference [2] set aside to
> discuss "User-visible Network Issues" - challenges that users face,
> that could benefit from both userspace and kernel enhancements to
> make their lives easier.
When you schedule this track, try to keep it off of November 3rd as
the core kernel network folk are holding netconf at LPC for that
entire day.
That is, unless you don't want any of us to attend :-)
next prev parent reply other threads:[~2010-09-17 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 19:12 Linux Plumbers Conference: User-visible Network Issues Mini-Conf Matt_Domsch
2010-09-17 22:57 ` David Miller [this message]
2010-10-15 19:50 ` Matt Domsch
2010-10-16 8:18 ` David Miller
2010-10-16 14:04 ` Matt Domsch
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=20100917.155746.171491800.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Matt_Domsch@Dell.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;
as well as URLs for NNTP newsgroup(s).