From: Daniel Borkmann <email@example.com>
To: firstname.lastname@example.org, email@example.com
Cc: firstname.lastname@example.org, email@example.com,
Subject: LPC 2022 Networking and BPF Track CFP
Date: Tue, 26 Apr 2022 22:59:18 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
We are pleased to announce the Call for Proposals (CFP) for the Networking and
BPF track at the 2022 edition of the Linux Plumbers Conference (LPC), which is
planned to be held in Dublin, Ireland, on September 12th - 14th, 2022.
Note that the conference is planned to be both in person and remote (hybrid).
CFP submitters should ideally be able to give their presentation in person to
minimize technical issues if circumstances permit, although presenting remotely
will also be possible.
This year's Networking and BPF track technical committee is comprised of:
David S. Miller <email@example.com>
Jakub Kicinski <firstname.lastname@example.org>
Paolo Abeni <email@example.com>
Eric Dumazet <firstname.lastname@example.org>
Alexei Starovoitov <email@example.com>
Daniel Borkmann <firstname.lastname@example.org>
Andrii Nakryiko <email@example.com>
We are seeking proposals of 40 minutes in length (including Q&A discussion).
Any kind of advanced Linux networking and/or BPF related topic will be considered.
Please submit your proposals through the official LPC website at:
Make sure to select "eBPF & Networking" in the track pull-down menu.
Proposals must be submitted by August 10th, and submitters will be notified of
acceptance by August 12th.
Final slides (as PDF) are due on the first day of the conference.
We are very much looking forward to a great conference and seeing you all!
next reply other threads:[~2022-04-26 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 20:59 Daniel Borkmann [this message]
2022-07-14 21:19 ` LPC 2022 Networking and BPF Track CFP (Reminder) Daniel Borkmann
2022-08-04 16:52 ` LPC 2022 Networking and BPF Track CFP (Final Reminder) Daniel Borkmann
2022-08-08 18:54 ` Followup from LSF/MM/BPF on standardization/documentation Dave Thaler
2022-08-11 17:23 ` Dave Thaler
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).