From: Jamal Hadi Salim <jhs@mojatatu.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org,
info@netdevconf.org, linux-wireless@vger.kernel.org,
tech-committee@netdevconf.org, David Miller <davem@davemloft.net>,
Stephen Jaworski <jaws@mojatatu.com>, Rob Echlin <rob@echlin.ca>,
lwn@lwn.net
Subject: ANNOUNCE: Netdev 2.1 update Feb 06
Date: Mon, 6 Feb 2017 08:02:51 -0500 [thread overview]
Message-ID: <bb5b53b7-ae46-e08c-f996-2dbc96fa1c29@mojatatu.com> (raw)
A few announcements:
- We expect to open up registration and announce hotel and location
this week.
- We are pleased to announce the first netdev 2.1 sponsor!
Many thanks to Mellanox who has been a strong supporter of the netdev
community. Mellanox is first to cross the netdev2.1 sponsor line with a
silver.
The Call for Proposals is still open, submit early
to avoid the hazards of last minute traffic. Refer to:
http://netdevconf.org/2.1/submit-proposal.html
cheers,
jamal
reply other threads:[~2017-02-06 13:02 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=bb5b53b7-ae46-e08c-f996-2dbc96fa1c29@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=davem@davemloft.net \
--cc=info@netdevconf.org \
--cc=jaws@mojatatu.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=rob@echlin.ca \
--cc=tech-committee@netdevconf.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