From: Daniel Borkmann <email@example.com> To: firstname.lastname@example.org, email@example.com Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: LPC 2021 Networking and BPF Track CFP (2nd reminder) Date: Fri, 6 Aug 2021 21:50:36 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> This is a reminder for the Call for Proposals (CFP) for the Networking and BPF track at the 2021 edition of the Linux Plumbers Conference (LPC), which will be held virtually on the wider Internet, on September 20th - 24th, 2021. This year's Networking and BPF track technical committee is comprised of: David S. Miller <email@example.com> Jakub Kicinski <firstname.lastname@example.org> Eric Dumazet <email@example.com> Alexei Starovoitov <firstname.lastname@example.org> Daniel Borkmann <email@example.com> Andrii Nakryiko <firstname.lastname@example.org> We are seeking proposals of 40 minutes in length (including Q&A discussion), optionally accompanied by papers of 2 to 10 pages in length. Any kind of advanced Linux networking and/or BPF related topic will be considered. Please submit your proposals through the official LPC website at: https://linuxplumbersconf.org/event/11/abstracts/ Make sure to select "Networking & BPF Summit" in the Track pull-down menu. Proposals must be submitted by August 13th, and submitters will be notified of acceptance by August 16th. Final slides and papers (as PDF) are due on the first day of the conference.
prev parent reply other threads:[~2021-08-06 19:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-06 15:27 LPC 2021 Networking and BPF Track CFP Daniel Borkmann 2021-07-06 19:33 ` LPC 2021 Networking and BPF Track CFP (Reminder) Daniel Borkmann 2021-08-06 19:50 ` Daniel Borkmann [this message]
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: LPC 2021 Networking and BPF Track CFP (2nd reminder)' \ /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
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).